After you’ve created a pipeline, you can monitor its execution history to ensure data is flowing as expected and to troubleshoot any issues. The execution log is your primary tool for understanding the health and status of your pipelines.
info
Execution logs show the outcome of each run (success, failure, or another status) and provide timestamps and error details. Use these logs to diagnose problems and verify your schedules.
Navigate to Pipelines: From the main sidebar, go to the Pipelines page. The Last Result column shows a summary status of the most recent run for each pipeline.
View the Execution Log: Click the three vertical dots on a pipeline and select View Executions. This will take you to a detailed log showing a history of all runs for that pipeline.
Inspect a Single Run: Click on any run in the log to open its detail page. Here you will find a step-by-step Event Log that shows what occurred during the execution, which is essential for troubleshooting.
View the Data: From the execution detail page, you can also download the data files from the run. For more information, see the Viewing Execution Data guide.
The status of a pipeline run tells you its current state or final outcome. The main Pipelines page shows a simplified summary, while the detailed execution log provides more specific statuses.
Status
Meaning & Context
Recommended Action
Scheduled
The pipeline is idle and waiting for its next scheduled run time.
No action needed.
Pending
The execution has been triggered and is waiting in the queue to start.
No action needed.
Running
The pipeline is currently executing.
No action needed.
Ok / Target Finished Ok
The pipeline completed successfully. Data was fetched, parsed, and delivered.
No action needed.
Aborted / Source Aborted
The run was stopped, usually because no new data was available from the source. This is common and not necessarily an error.
No action needed unless you expected new data. Consider adjusting your Polling Rate.
Errored / Source Errored
An error occurred while fetching or parsing data from the source.
Inspect the run’s Event Log for specific error messages.
Errored / Target Errored
An error occurred while delivering data to the target.
Inspect the Event Log for error details. Check your target integration’s configuration.
Errored / Source Errored Fatal
A critical, non-recoverable error occurred at the source. The pipeline will not retry automatically.
Fatal errors indicate something went wrong outside of your configuration. Our development team is notified automatically. It may be related to the source or target platform. Check the dashboard or status page for known outages. If the issue persists, reach out to us for support.
Errored / Target Errored Fatal
A critical, non-recoverable error occurred at the target. The pipeline will not retry automatically.
Fatal errors indicate something went wrong outside of your configuration. Our development team is notified automatically. It may be related to the source or target platform. Check the dashboard or status page for known outages. If the issue persists, reach out to us for support.