Skip to main content
Every time Nekt triggers the extraction of a source, the execution of a query, notebook, or history, or sends data to a destination, it creates a run. Runs are the unit of execution for your data pipelines. You can monitor runs to make sure processes complete successfully and to diagnose issues when something goes wrong.

​
What is a run?

A run is a single execution of a pipeline step, such as:
  • Source extraction
  • Query execution
  • Notebook execution
  • History execution
  • Destination load
Each time a pipeline is executed (manually, on a schedule, or via a trigger), a new run is created. You can track its progress and inspect its logs if something fails.

​
What can I do on the Runs page?

On the Runs page you will find:
  • A list of recent runs with their status (e.g. succeeded, failed, running).
  • The pipeline name and type (source, query, notebook, history, destination).
  • Key metadata such as start time, duration, and trigger type.
You can filter the list by status and/or by pipeline, so you can quickly focus on failures or on specific pipelines you care about. For details on reading logs, retry behavior, and alerts, see Logs.