Runs
Follow every time an IDP template processed a document: environments, statuses, stats and each run's details, trace and logs.
Runs
The Runs tab lists every time the template processed a document, and what happened each time. Only workspace developers and administrators can see a template's runs.
Environments
Runs are split by environment, because a failure in the Playground and a failure in production are read very differently. Pick the environment in the selector at the top; the tab opens on Development.
| Environment | What feeds it | Configuration used |
|---|---|---|
| Production | Calls through the API and webhook, the robot action and the AI agent action. See Using templates in automations. | The active version. |
| Development | The Playground and Simulate API. | The draft. |
| Testing | The evaluation sets. | The draft. |
Run list
Runs are listed from newest to oldest, 20 per page. Each row shows:
- the name of the processed document (or No document) and how long ago the run started;
- the via API or via Webhook tag, when the run came from an external call;
- in the Testing environment, the case's verdict: Passed or Failed;
- the status and the duration.
While a run is queued or in progress, the list refreshes itself every few seconds. Use Refresh to reload at any time.
Statuses
| Status | Meaning |
|---|---|
| Awaiting upload | An API call reserved the run, but the document has not been uploaded yet. |
| Queued | The document arrived and the run is waiting to start. |
| Running | The pipeline is processing the document. |
| Finished | The pipeline reached the end. This includes documents rejected by identification and results that failed validations: they are valid outcomes, not errors. |
| Failed | The run ended with an error, for example a model failure, an error in a post-processing script or an unsupported file format. The message shows in the details. |
| Expired | The document for an API call was not uploaded in time, and the reservation expired. |
Stats
Above the list, three stats sum up the selected environment:
| Stat | How it is calculated |
|---|---|
| Runs | How many runs the environment has. |
| Success rate | The percentage of Finished runs among those that ended (Finished or Failed). |
| Average duration | The average duration of the runs that have ended. |
Run details
Click a run to open the panel with its start date and time, its status and three tabs.
Details
| Item | Description |
|---|---|
| Test result | Testing environment only: Passed or Failed. |
| Document | The name and format of the processed file. |
| Pages | The pages requested by the call, when it set the page field. |
| Parameters | The parameters sent with the call, if any. |
| Output | The pipeline's final output: the last post-processing step's output or, without one, the extracted text. |
| Error | The error message, when the run failed. |
| Environment, Started, Finished and Duration | Where and when the run happened and how long it took. |
Trace
Trace shows the pipeline tree as it ran: the document received and, under it, each stage that ran, with its filters, steps and validations. Stages that never ran are left out; when identification rejects the document, it is marked as Aborted. Failed validations show their reason next to their name.
Click any item to see the value recorded — for example the extracted text, a step's output or a validation's answer — Pretty or Raw. Images, such as the pre-processing previews, show as images.
Logs
Logs show the same path as lines, one per step, with the time since the start of the run and each step's duration, for example [+1520ms] Extraction (840ms). The time since the start is calculated by adding up the stages' durations, in pipeline order.