Task and processing statuses
This page lists the status values used by Dafne. Statuses are shown in the Monitor console and determine which actions are offered.
Contents
Scheduled task statuses
A scheduled task is one instance of a Task within one Processing. It carries its own status, independent of the task definition.
| Status | Meaning | Counted as |
|---|---|---|
| Scheduled | Planned for the current processing and waiting to be picked up. | Waiting |
| Repeat | Queued for another attempt, keeping all normal constraints. | Waiting |
| Force repeat | Queued for another attempt as soon as possible, bypassing the normal waiting rules. | Waiting |
| On hold | Deliberately kept out of the queue by an operator. It will not be picked up until it is released with Unhold. | Waiting |
| Prepared | Selected for execution but not yet started. A short-lived technical state. | Running |
| Running | Currently executing. | Running |
| Cancelling | A cancel has been requested. | Running |
| Cancel in progress | The cancel is being carried out. | Running |
| Finished | Completed successfully. | Success |
| Manual finished | Marked as complete by an operator. Treated as success, so dependent tasks may start. | Manual |
| Warning | Completed, but the execution reported a condition configured to be treated as a warning. | Warning |
| Error | The previous attempt ended with an error. | Error |
| Cannot connect | The previous attempt failed while connecting to the target system. | Error |
| Invalid | A technical state that occurs when the executor stops while the task is running or prepared. | Error |
| Repair | A repair run has been requested. Only for connection providers that support repair. | Waiting |
| Ignored | Excluded from the processing. | |
| Not scheduled | Not part of the current processing. |
The Counted as column shows which counter on the Monitor console the status contributes to. Statuses without a value are not aggregated into the processing counters.
Which actions each status allows
The action menu on a scheduled task only offers what is currently valid. In general:
- Repeat and Force repeat apply to a task that has finished in some way and can be run again
- Cancel applies to a task that is running
- Set complete applies to a task that has not completed successfully
- Hold applies to a task that is waiting; Unhold to one already on hold
Two further conditions apply to all of them. The executor must be running, and the processing must be active. When either is not true, the menu shows Scheduler stopped or Processing not active and the actions stay disabled.
Processing statuses
A Processing is one planned run of a scenario for a given date and iteration.
| Status | Meaning |
|---|---|
| Waiting | The scenario has not triggered yet. The Monitor shows the time it will start at and, for SQL-based planning, the polling details. |
| Running | Tasks are being executed. |
| Paused | Execution is suspended. No new task will be started; other processings are unaffected. |
| Finished | All tasks have reached a terminal state. |
| Reschedule | A reopen has been requested and the processing is waiting for the executor to re-plan it. |
| Manual run requested | A manual run has been requested and is waiting to be picked up. |
| Manual paused run requested | A manual run has been requested that will start in paused state. |
Executor statuses
The executor is the component that plans and runs tasks. Its status is shown on the button in the Monitor console filter bar.
| Status | Meaning |
|---|---|
| Running | Normal operation. Scenarios are planned and tasks executed. |
| Paused | No new scenarios are planned and no new tasks are started. Tasks already running continue. |
| Stopping | A stop has been requested. The executor waits for running tasks to finish before it stops. |
| Stopped | Not running. The status button is disabled in this state. |
| Killing | A forced stop is in progress. |
See Executor control for when to use each transition.
