Articles in this section

Investigate & troubleshoot errors

Anitha Abraham
Updated

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. 

Prerequisites

  • Permissions: You need 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. Debug logs and advanced diagnostics may vary by plan.

Tools to troubleshoot errors

overview-em.png

When an error occurs after a flow runs, look for cues in three places: the Errors page, Flow builder, and the Developer playground / Advanced Field Editors (AFEs). The table below maps each diagnostic tool to where you'll find it and how to use it.

Tool What it does When to use it How to use it
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.

  1. Click the error count in an integration from your dashboard or home page. It opens the Errors page.
  2. Review error details & use Celigo Ora (AI support) for guidance on error resolution.
  3. Edit the retry data.
  4. Retry the error.

For more information, see Troubleshoot errors with Celigo Ora
Audit logs Records resource modifications made by any user. When a previously working flow fails and you suspect a configuration change.
  1. Select the integration.
  2. Click the Audit log tab.
  3. Filter by date or user to find the change that caused the error.

    4. For more information, see View or download audit logs

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.

  1. In Flow builder, go to Run history.
  2. Click the Run logs icon next to a flow step.
  3. Use Trace view to follow a record end to end.

    4. For more information, see Introduction to execution logs

Debug logs (for HTTP connectors) Captures HTTP request and response details for connections. For API troubleshooting on HTTP, Salesforce, or NetSuite connector errors.

  1. Select a flow step with the error & enable debug.
  2. Run the flow.
  3. Review the request and response in the log.

For more information, see Debug flow steps & Debug connections
Diagnostics Produces a downloadable ZIP with configuration snapshots. For deep-dive analysis or when sharing configuration with a colleague or Support.

  1. Select the flow with error in your integration.
  2. Go to the Run console, click Actions (...)
  3. Click Download diagnostics for the file. which includes flow run details such as export, import, parent job, child job details.
Developer playground /Advanced Field Editors (AFEs) Performs real-time syntax checking for JavaScript and Handlebars. When an error points to a script in a hook, filter, or mapping.

  1. Launch the advanced field editor on the relevant step (or from Playground).
  2. Paste your script to see syntax errors inline. Use Celigo Ora to try and resolve your errors.

    3. For more information, see Advanced field editors (AFEs) and the Playground