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 stage.
The following table represents a general approach from error detection to resolution. You can use this sample approach or a similar one to ensure that 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 | Get notified of errors only when you're subscribed to the notification mails. However, when you're assigned errors, you'll be automatically notified. | 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.
Automate error management with custom flows & templates
You can build custom flows and automate your error management. The following examples & template could help you to create solutions based on your scenarios and requirements.
| Flow/template | What it means |
| 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 | Write JavaScript hooks inside a custom flow to auto-ignore a known error. |
| Send errors to an integrator.io listener using a postSubmit hook | Write JavaScript hooks inside a custom flow to send error data to an external listener. |
| Generate a report of flow events (available Celigo platform option) | Pull a built-in report of every event, success or error, that ran through one or more flows. |
| 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 | Use the "Error automation via integrator.io APIs" template — install a Marketplace template that auto-resolves or auto-retries matching errors from outside the flow, using the integrator.io API. |
Proactively manage errors with debug & test options
A related set of error-management tools helps you catch problems before flows go live and reach production, or dig into exactly what a connection or flow step sent and received. They often help during investigation and are worth knowing about:
- Debug flow steps and debug a connection — capture the request/response traffic for a flow step or an entire connection.
- Run a test flow and review the test run results — run a flow against mock or live data before enabling it, and review what happened.
- Provide mock data for testing flows in the integrator.io canonical format for JSON — the mechanics behind test data.