troubleshooting-flows

What problem does it solve?

Troubleshooting-flows helps you diagnose why a Celigo flow fails, partially fails, returns no records, or runs slowly so you can restore correct processing quickly and systematically.

Core Features & Use Cases

• Flow health triage by job status: distinguish total failure, partial failure, empty runs, stuck jobs, and intermittent behavior using job metrics like success/error counts and page generation/processing.
• Error pattern diagnosis: group errors by message pattern to identify root causes instead of manually reading thousands of messages.
• Record-level and HTTP-level inspection: inspect execution logs, per-step errors, and raw request/response details to confirm configuration issues vs data-dependent issues.
• Safe iteration and production-grade tracing: use test runs for fast, low-risk verification, then use end-to-end tracing for silent logic bugs or production incidents.
• Fix and recovery workflow: retry failed records, resolve expected errors, update retry data for specific failing records, and verify the fix with clean re-runs.

Quick Start

Ask the AI to help you diagnose a failing flow by first checking the most recent job status and identifying which step has the highest error count, then analyze error patterns and inspect the raw request/response for the failing step.