Q. How can concurrency ID lock delay flow run completion?
For import flow steps, the concurrency ID lock template determines if multiple records can be processed parallel or not. Any field from the export response data can be used as a concurrency ID template, but if the same field value is used for multiple records then those records are serially processed.
For Amazon - NetSuite, integrator.io uses a trace key with a unique value for each record as the concurrency ID lock template. The records that do not have a unique trace key value are processed serially causing delay in flow run completion.
Solution: Define a unique concurrency ID lock for each record.
Please sign in to leave a comment.