When a record fails at an import step, you choose whether the flow holds the record at that step or sends it on to the next step. This article is for builders who run flows with more than one destination and need to control, isolate, and recover failed records.
Choose how a step handles failed records
- Open the flow in the flow builder.
- On the import step, select More
> Outgoing data > Error handling.
- Under What should happen to a record if the import fails?, select Pause or stop and return an error or Proceed to the next application regardless.
| Option | What happens to a failed record |
|---|---|
| Pause or stop and return an error | The step holds the record and doesn't send it to later steps. You fix and retry the record at this step. After a successful retry, the record continues to the later steps. This is the default. |
| Proceed to the next application regardless | The record continues to the later steps even though it failed here. You can still fix and retry it at this step, but a successful retry doesn't send it on to later steps that it already passed. |
Select Proceed to the next application regardless when later steps shouldn't depend on this one. For example, if you send inventory updates from NetSuite to several webstores and marketplaces, a failure in one store shouldn't stop the others from getting the update.
Isolate failed records
To capture a failed record as its own record-level error while the other records keep processing, set What should happen to a record if the import fails? to Proceed to the next application regardless. For an HTTP import, leave Number of records per HTTP request blank or set it to 1, so that each record is sent separately. This is the default.
Troubleshoot failed records
Failed records aren't in the next scheduled run
Symptom: A delta export doesn't send records that failed in a downstream import.
Cause: A downstream import failure doesn't roll back the delta export checkpoint, so the export doesn't include the records again unless the source record changes.
Resolution: Retry the records from error management. To resend records that have no completion marker, use a reconciliation or backfill flow. Add the completion marker only after the destination confirms a successful import.
The dashboard doesn't show the endpoint's error response
Symptom: A record fails, but the integration dashboard doesn't show why the endpoint rejected it.
Cause: Basic logging doesn't always capture the endpoint's error response.
Resolution: Turn on debug logs for the flow step to capture the HTTP request and response, and turn them off when you finish. To report application errors for individual records, configure HTTP response or error parsing on the import. For the dashboard, see Integration dashboard.
An error's source is Internal
Symptom: An error shows Internal as its source, for example NoSuchKey ("The specified key does not exist") or page_not_found.
Cause: The error comes from the Celigo platform, not from your flow configuration or the endpoint.
Resolution: Use Celigo Ora overview or the available diagnostic tools to confirm the source, and contact Celigo Support.