Records that fail

A record is one item a flow processes, such as an order, a product or a customer. When processing fails, the activity gets the status Failed and the dashboard shows how many records could not be processed.

What APIcenter retries automatically

APIcenter only retries a record by itself when the problem is temporary. The dashboard shows this under Resolved automatically, and the activity log with the trigger Automatic retry.

• The connection took too long: up to seven times, the last time about three days after the first error.
• The login failed: four times, the last time about 12.5 hours after the first error. See Connection to an application failed.
• The limit of the application was reached: at the moment the application indicates. See A flow is not running.

Errors you need to solve

Other errors are about the data itself. They are not solved by themselves, not even when you retry. Common causes:

• a required field is empty, for example an address, email address or item number;
• a value does not exist in the other application, such as a product, VAT code, payment method or shipping method;
• a value is not mapped in the data mapping;
• a setting is missing or wrong, see Flow settings;
• the other application rejects the record, for example because it already exists.

How to solve it

1. On the dashboard, click View errors, or filter on Status Failed on the Activity tab.
2. Open an activity and read the message of each item. It usually names the field or value that caused the error.
3. Do you not understand the message? Click Ask AI or Help with this error.
4. Solve the cause: in the application itself, in the settings or in the data mapping.
5. Click Retry. You can also retry sales orders in bulk on the Admin tab.

Tips

• Many records often have the same cause. Solve it once, then retry all records.
• Only retry a record when the cause is solved. Otherwise it fails again.
• Still stuck? Create a support ticket with the ID of the activity.