Integrations could hit an error due to a mismatched field, an expired credential, or a rate limit. Error management is how you stay on top of those errors: seeing them when they happen, deciding who handles each one, understanding why it occurred, and getting the record successfully processed. This article walks through an error management process and points to a focused article for each step.
Use the following process, or a similar one, so your team handles errors in a timely and effective manner.
| Steps | What it means | Where to go next |
|---|---|---|
| Monitor | Check for errors after flow runs, using the home page, dashboards, or the flow builder. | Monitor errors |
| Notify | Subscribe to notification emails to hear about errors as they occur. If an error is assigned to you, you're notified automatically. | Email notifications |
| Organize | Label errors with tags — for example, by priority or status — so your team can work through them systematically. | Tag errors |
| Delegate | Assign errors to yourself or a teammate for ownership and follow-up. | Assign errors |
| Investigate | Review error details, audit logs, and other diagnostic tools to identify the root cause. | Investigate errors |
| Retry/Resolve | Correct and retry any assigned errors for closure, or resolve errors to dismiss them. |
You don't have to work through every error manually. The Celigo platform (integrator.io)
automatically resolves and retries a meaningful share of errors on its own —
see How automatic error resolution works for what it handles without your intervention,
but it needs your trace key configured correctly to do so.
Your trace key is the account-level setting that lets integrator.io match retried records to their original errors, and auto-resolution refers to errors integrator.io clears on its own without manual action.
Automate error management with custom flows & templates
Custom flows and installable templates can handle error management steps without manual effort — Slack alerts, auto-ignoring known errors, and API-driven resolution among them:
| Flow/template | What it does |
| Send step errors to Slack using a flow | Build a custom flow that posts an open-error count to a team Slack channel. |
| Ignore specific flow errors | Add a JavaScript hook to a custom flow to auto-ignore a known error. |
| Send errors to an integrator.io listener using a postSubmit hook | Add a JavaScript hook to a custom flow to send error data to an external listener. |
| Consolidate errors in a single report | Install a template that gathers unresolved errors across your whole domain into one CSV, on demand or on a schedule. (for integration apps) |
| Use the error automation via integrator.io API | Install a Marketplace template that auto-resolves or auto-retries matching errors from outside the flow, using the integrator.io API. |
Tip: You can pull a built-in report of every event, success or error, that ran through one or more flows using the platform option, Generate a report of flow events.