The Celigo platform (integrator.io) provides several diagnostic tools, including error fields, audit logs, and execution logs, to help you identify root causes and troubleshoot flow errors or failures. The primary focus of this article is troubleshooting errors after flows have been enabled and run; but we also cover troubleshooting errors that occur while building and testing your flows, that is, before you run live flows.
-
Permissions: You must have at least Monitor access to view dashboards and error lists. Admin or Manage access is required to view audit logs, execution logs, or use the Developer playground.
-
Subscription plan: Standard, Professional, or Enterprise edition. (Note: Debug logs and advanced diagnostics may vary by plan).
-
Before enabling & running a flow: You can use mock data, previews, and test runs in Flow Builder to verify that your flow handles the expected data before it processes real records.
-
After running a flow: When errors occur after flow runs, you can find cues or hints for troubleshooting in the following places:
-
Errors page: important details in the error fields; and, in the case of some connections, such as HTTP, Salesforce, and NetSuite, you can find request and response details also.
-
Flow builder: details in audit logs, execution logs, debug logs, and diagnostics.
-
Developer playground: details in the Advanced Field Editor (AFE) for Handlebars helpers and script issues.
-
|
# |
Tool |
What it does |
When to use it |
How to use it |
|---|---|---|---|---|
|
1 |
Mock data |
Simulates input records without calling your live source system. |
While configuring exports, lookups, or imports, before any real flow run. |
When building or configuring a flow step in Flow builder,
See also, Auto-generate mock data |
|
2 |
Preview |
Shows a live sample of how actual or mock data moves through a step. |
When fine-tuning field mappings or filters mid-build. |
When building or configuring a flow step in Flow builder, See also, Preview import data |
|
3 |
Test run |
Runs the flow once in test mode using real or mock data. |
Before enabling a flow in production. |
When building or configuring a flow step in Flow builder,
See also, Test flow runs |
|
# |
Tool |
What it does |
When to use it |
How to use it |
|---|---|---|---|---|
|
1 |
Error fields (AI support) |
Shows the source, timestamp, classification, and trace key for each error. |
As your first stop, for immediate troubleshooting of any error. |
See aslo, Troubleshoot errors with Celigo Ora |
|
2 |
Audit logs |
Records resource modifications made by any user. |
When a previously working flow fails and you suspect a configuration change. |
See also, View or download audit logs |
|
3 |
Execution logs (run logs) |
Provides step-level status and timing for each stage of a flow run. |
When you need detailed, per-record visibility into how a flow executed. |
See also, Introduction to execution logs |
|
4 |
Debug logs (for HTTP connectors) |
Captures HTTP request and response details for connections. |
For API troubleshooting on HTTP, Salesforce, or NetSuite connector errors. |
See also, Debug flow steps & Debug connections |
|
5 |
Diagnostics |
Produces a downloadable ZIP with configuration snapshots. |
For deep-dive analysis or when sharing configuration with a colleague or Support. |
|
|
6 |
Advanced Field Editor (AFE) |
Performs real-time syntax checking for JavaScript and Handlebars. |
When an error points to a script in a hook, filter, or mapping. |