Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ingestly.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Runs page shows all runs across your organization. You can also view runs for a specific pipeline from its detail page.

​
Exporting runs

Click Export to CSV above the runs table to download the current view. If you have rows selected, only those rows are exported. This is useful for sharing a specific set of runs with a teammate or attaching them to a ticket.

​
Filtering runs

Use the status filters to narrow the list:
  • All: show all runs
  • Queued: waiting to start
  • Running: currently executing
  • Completed: finished successfully
  • Failed: encountered an error
  • Review: paused for human review
  • Cancelled: manually cancelled
  • Awaiting Children: waiting for child runs from document chunking to complete

​
Run detail

Click a run to view its details. The run detail page shows:

​
Step timeline

A visual timeline of each pipeline step and its status. Steps are shown in run order with timestamps. Use the Show skipped toggle in the navigator to show or hide steps that were skipped during this run.

​
Step data

Click a step in the timeline to inspect:
  • Input: data received from the previous step
  • Output: data produced by this step
  • Errors: error details if the step failed
  • Timing: start time, end time, and duration
  • Credits: credits charged to this step
  • Skip reason: when a step was skipped, a brief explanation of why (for example, the step was bypassed by a route condition)

​
Document viewer

For runs with extraction results, the document viewer renders the source document beside the extracted fields and supports:
  • Bounding box overlays: colored rectangles show where each field was found. When a value spans multiple lines, each line gets its own rectangle so the highlight tracks the actual text rather than a single bounding box that covers unrelated content.
  • Field info popovers: hover any bounding box to see the field name, the extracted value, and the confidence score.
  • Rotate: if a scan came in sideways or upside down, use the rotate control in the viewer toolbar to spin the page 90° at a time. The rotation is local to your view; the source document is not modified.

​
Test mode previews

When a pipeline runs in test mode, output nodes show previews instead of sending real outputs.
  • Callback steps show the resolved URL, request headers, and request body preview
  • Email steps show the recipients, subject, body preview, and attachment names
Test mode previews help you verify output configuration before you enable real outputs.

​
Callback history

If the pipeline includes a callback output node, the run detail page shows a Callback History panel. This displays each callback attempt with:
  • URL: the webhook endpoint that was called
  • Status code: the HTTP response status
  • Success/Failure: whether the callback was delivered successfully
  • Attempt number: callbacks are retried on failure

​
Run actions

The actions menu on each run row offers:
  • Cancel: stop a running or queued run
  • Go to pipeline: navigate to the parent pipeline
  • Go to document: navigate to the source document
  • Download output: download the captured payload as a JSON file. Only available when the pipeline includes a Download output node and the run reached it

​
Testing from the editor

You can start a run directly from the pipeline editor.
  • Select a document from the run toolbar
  • Use documents in Uploaded, Completed, or Failed status
  • Choose Test mode for preview-only outputs or Real mode for live outputs

​
Pipeline timer

When viewing a run in the pipeline editor, a timer badge appears in the top-right corner of the canvas:
  • Running: a blue badge shows elapsed time, updating in real time
  • In review: an amber badge indicates the run is paused for human review
  • Completed: a green badge shows the total processing time
  • Failed: a red badge shows the time elapsed before the failure

​
Child runs

When a document is split into chunks, each chunk is processed as a separate child run. Child runs appear as expandable rows in the runs table: click the expand icon on a parent run to see its child runs inline. In the run detail view, use the sub-run navigator to page through sibling child runs without returning to the table. The navigator shows the current child run’s index and lets you step forward or backward through the set.

​
Real-time updates

Run status and step progress update in real time via SignalR. Both the runs list page and the run detail view receive push updates, so you see changes as they happen without refreshing the page.