Tasks
The Tasks page shows the runner task queue. A Task is one unit of work a Runner claims for one node instance. Open Monitoring, then Tasks (/admin/monitoring/tasks).
Reading the queue
Tiles count the queue by state: Pending, In progress, Retrying, Failed and Completed. A Failed tasks panel lists recent failures for you to investigate before you prune anything.
The Recent activity table lists tasks with their state, the node and session they belong to, the runner type, the retry count and when they last changed.
| State | Meaning |
|---|---|
| Pending | Queued and waiting for a runner to claim it |
| In progress | A runner is working on it now |
| Retrying | A run failed and the platform will try again |
| Failed | The last run failed. Open the node for details |
| Completed | Finished |
A long list of Pending tasks with nothing In progress means no runner is claiming that kind of work. Check the runner deployment on Cluster and Runners. A session that keeps producing Failed and Retrying tasks is in a churn loop and needs its inputs or template corrected.
Task actions
Each row offers two actions:
- Release claim returns a claimed task to the queue so another runner can pick it up.
- Delete task removes one task row.
Deleting a task removes only the queue row, not the session or its outputs. Investigate a failure before deleting it, or wait for retention to clear it.
Queue pruning
Task rows accumulate as history. On a long-running environment the queue grows without bound and the page slows down. Queue pruning deletes aged task rows only. It never touches sessions, node outputs, stored data or dimensions, so it is safe to leave on.
Pruning is controlled by platform configuration keys under system.tasks.prune, set on the Configuration page. The maintenance panel on this page previews and runs a sweep where enabled.
Claimed and Retrying rows are never pruned, because they represent work in flight. Keep the Failed window at seven days or more so you can still diagnose recent failures.
Pruning is not session retention. Retention removes session outputs and whole sessions according to the template’s policy. Pruning removes only task history.