Introduction

A run represents one execution of a pipeline, triggered when a document is submitted to it. Each run tracks the progress and results of every step in the pipeline.

​

Run lifecycle

Runs move through the following statuses:

​

Step executions

Each node in the pipeline produces a step execution within the run. A step execution records:

• The node type and configuration used
• Start and end timestamps
• Status
• Input data received from the previous step
• Output data produced for the next step
• Processing time
• Error details (if failed)

​

Step execution statuses

You can inspect individual step executions in the run detail view to debug issues or review extracted data.

​

Document chunking

When a document is split into chunks (e.g., a multi-page PDF split into individual pages), Ingestly creates child runs for each chunk. The parent run enters the Awaiting Sub-runs status until all child runs complete. Each child run processes its chunk independently through the pipeline. The parent run tracks:

• Child runs: individual processing runs for each chunk
• Chunk index: the position of each chunk in the original document
• Chunk label: a descriptive label for the chunk

​

Credits

Each run consumes credits based on the actions performed. Credit usage depends on the node types in your pipeline and the complexity of the processing.

​

Callbacks

When a run completes and the pipeline includes a callback output node, Ingestly sends the results to your configured webhook URL. See webhooks and callbacks for details.

​

Real-time updates

Ingestly uses SignalR to push real-time status updates to the UI. When you view a run, you see step progress and status changes as they happen. No need to refresh the page.

​

Managing runs

You can view runs globally across all pipelines or within a specific pipeline. The Runs page provides filtering by status and access to run details.