integrator.io gives you several places to check on a flow's health, whether it's still running or finished a while ago, and several paths to drill down from a high-level count all the way to the errors themselves. This article covers the Home page, the account and integration dashboards, the flow-level Run console and Run history, and the Analytics tab. For setting up email alerts instead of checking manually, see Set up error notifications. For working directly with individual errors once you've drilled down to them, see Understand the Errors page.
Prerequisites:
- Permissions — You need Admin, Manage All, or Monitor All permissions to access dashboards and flow history.
- Setup — You need at least one active flow in your account to generate metrics.
- Data retention — How long flow history and error retry data are stored depends on your account's data retention plan: 30 days by default, up to 180 days depending on your plan.
Monitor from the Home page
The Home page's list view shows every integration in a row, with its current error count and other details at a glance — a quick, big-picture way to spot which integrations need attention before you drill into any one of them.
- Sort integrations by Status to see error counts in ascending or descending order.
- Pin an integration to keep it at the top of the list, marked with a gray pin icon.
- If all of an integration's errors sit in a single flow step, select the error count directly to jump straight to that step's Errors list, from either the Home page or Flow Builder.
Drill down from an integration
Selecting an integration's name or error count from the Home page opens that Integration page (on its Flows tab by default), listing every flow and its errors. From there, you can drill down to the flow-step level two ways:
- Via the flow's Name link — Opens the flow in Flow Builder, where you can see flow steps visually alongside run details (Run console, Run history, connection, audit log, and flow settings) before selecting an error count to jump to the Errors page. This path is useful when you want to investigate using both Flow Builder and the Errors page together.
- Via the error count or errors link — Takes you directly to the flow page's step list, and from there to error details for a step. This path is useful for quick troubleshooting when the Errors page details are enough on their own, or when you recognize the error from before.
Breadcrumbs at the top of the screen show the navigation path — for example, the path to a specific integration — so you can move between pages without losing your place.
Dashboards
Dashboards give you an account-wide or integration-specific view of flow activity, and are another entry point into Run history.
-
Account-level — Go to Dashboard
to see details for every integration across your account.
- Integration-level — From within a specific integration, select its Dashboard tab to see metrics scoped to that integration.
The Dashboard splits activity into:
- Running flows — Flows currently in progress, with real-time counts of successful, ignored, and error records.
- Completed flows — Results for flows that finished within a selected date range. The open-errors count reflects the current historical total for that flow, not just the errors produced by the specific run you're looking at.
Select a flow's Run number from either dashboard to open Run history at the flow and flow-step level, filterable by date range or status.
Run console and Run history
For a closer look at a specific flow's executions, open the flow and use its Run console and Run history.
- Run console — Select a flow within an integration to open the Run console on its first tab. You can watch a flow while it runs and see errors before the run finishes. The console only reflects the most recent or currently active run — resolving errors elsewhere doesn't update these counts.
- Run history — Select the Run history tab beneath a flow, or select the number in a dashboard's Runs column.
Run history behavior:
| Aspect | Behavior |
|---|---|
| Retention | Shows the last 1,000 runs, or follows your account's data retention limit — whichever is shorter. |
| Static details | History records don't update after the fact. If you later resolve 100 errors from a past run, that run's history still shows 100 errors produced. |
| Status codes | Color-coded badges: Completed (green), Completed with errors (yellow badge labeled Completed, with a warning icon), Canceled (blue), or Failed (red). |
Filter Run history using:
- Select range — A preset time range (for example, Last 7 Days) or a custom range.
- Select status — Limit the list to specific outcomes, like errors or cancellations.
- Hide empty runs — Exclude runs where Success, Ignored, and Errors are all 0.
For deeper investigation of a specific run's errors, see Troubleshoot errors: root cause analysis and diagnostic tools.
Monitor from email notifications
If you've set up notifications for flow errors (see Set up error notifications), you can act on them directly from the email: select a message link to jump to the Errors page, or select the flow step to jump to Flow Builder.
Access errors through the API
You can retrieve and manage errors programmatically through the integrator.io API — for example, to build a custom alert or an automated resolution routine in an external tool like Slack. The API returns up to 1,000 records per call; use pagination to retrieve more. See Use the "Error automation via integrator.io APIs" template for a ready-made automation.
Analyze flow metrics
Select the Analytics tab within an integration to see charts of successes, ignored records, and average processing time. Use these to spot performance trends or unusual spikes in error activity.
The chart's time interval adjusts to the range you're viewing:
| Time range | Interval shown |
|---|---|
| 4 hours or less | One-minute intervals |
| 4 hours to 4 days | Hourly intervals |
| More than 4 days | Daily intervals |
Select the flow selector at the top right of the chart (it shows Integration-level by default) to choose up to eight flows to compare on the same chart.