The Celigo platform (integrator.io) provides monitoring and analysis tools that let you track flow performance, investigate execution details, and resolve system exceptions. These features are available to all builders and administrators to ensure data integrity across your integrations.
Before you can monitor or analyze flow runs, ensure you meet the following requirements:
-
Permissions: You must have Admin, Manage All, or Monitor All permissions to access dashboards and flow history.
-
Setup: You must have at least one active flow configured in your account to generate metrics.
-
Plan requirements: Your data retention plan determines how long flow history and error retry data are stored (typically between 30 and 90 days).
You can monitor running flows and view the results of completed runs in two primary locations: Dashboards or Flow builder (Run console & run history)
-
Go to Dashboard on the left navigation menu to see details for all flows across your account. You can filter the view by integration, environment, or status.
-
Within a specific integration, select the Dashboard tab to see metrics specific to that integration.
|
Running flows |
Displays flows currently in progress, including real-time record counts for success, ignored, and error states. |
|
Completed flows |
Shows results for flows that finished within a selected date range. Open errors reflect the current historical total, not just the errors from that specific run. |
For granular details on specific executions, use the Run console and Run history.
Select a specific flow from within an integration to view the Run console on the first tab. You can watch the flow as it runs and access errors before the run completes.
Note
The Run console only reflects the status of the most recent or active run. Resolving errors elsewhere is not reflected in these counts.
Select the Run history tab beneath a flow configuration or select the number in the Runs column from any dashboard.
|
Feature |
Behavior |
|
Retention |
Displays the last 1,000 runs or follows your account's data retention limit. |
|
Static details |
History contains static details. If you resolve 100 errors from a past run, the history record will still show 100 errors were produced. |
|
Status codes |
Uses color-coding to indicate Success, Completed with errors, Canceled, or Failed. |
Run history – filters
You can use the following options to refine the history view:
-
Select range: Choose a preset time range, such as Last 7 Days, or set a custom range.
-
Select status: Filter the list to see only runs with specific outcomes, like errors or cancellations.
-
Hide empty runs: Turn on this toggle to exclude jobs where the Success, Ignored, and Errors columns are all
0.
For more run details to investigate errors, see also Execution logging.
You can use the integrator.io API to manage errors programmatically. This lets you build custom alerts or automated resolution routines in external tools like Slack. For more details on APIs , see Errors & status codes and flow errors.
The API returns up to 1,000 records per call. Use pagination to retrieve additional records.
integrator.io checks for new and resolved errors every 15 minutes. You can set up email notifications to receive a summary of these changes.
-
Choose an integration in which you want to set error notifications for flows.
-
Select the Notifications tab. Subscribe to error alerts to receive summaries of new, resolved, and open errors. If you use multiple environments, you must subscribe to notifications separately in your production and non-production environments.
-
Under Notify me of flow errors, check the box next to the required flows.
-
Under Notify me when connections go offline, check the box next to the required connections.
-
Click Save.
If you're admin, you can set notifications for other users in your team. For more details on notifications, see Email-notifications.
Select the Analytics tab within an integration to view visual charts of successes, ignores, and average processing time. These charts help you identify trends and performance bottlenecks.
|
Time range |
Interval display |
|
4 hours or less |
Results displayed in one-minute intervals. |
|
4 hours to 4 days |
Results displayed in hourly intervals. |
|
More than 4 days |
Results displayed in daily intervals. |
You can select the button on the top right to choose up to eight data streams to compare in the charts.