Skip to main content
Every integration follows the same pattern: a Scheduler triggers a Route, the Incoming configuration fetches data from the source and creates tasks, and the Outgoing configuration picks up those tasks and sends the data to the destination.
Open the task from the Tasks overview and check the Logs tab. It will show exactly what went wrong, for example a 500 error from the destination API or a misconfigured transformer.
A Failed task encountered an error during processing. A Skipped task was intentionally not sent because a filter on the Outgoing configuration matched –– it is considered done, not broken.
Check the Total throughput time on the Queue page to see how long the process actually takes, then increase the Scheduler interval so it is longer than the process duration.