For the dispatcher, tasks are work orders, notices, or automatically executed steps. The underlying technical implementation is not relevant here. What matters is when tasks appear, what they mean, how they are executed, and how their status is to be interpreted.
How tasks are created
Tasks are not created manually but are generated from predefined task templates of the dispatch center. Whenever an operation changes, the system automatically checks which task templates apply to that operation. This happens, among other things, when:
The operation location changes
Resources are added or removed
Keywords change
An operation is dispatched
If a rule applies, the corresponding task is automatically added to the operation. If it no longer applies, it is removed again.
OPTIONAL and REQUIRED tasks
Tasks are weighted differently from an operational perspective.
OPTIONAL tasks are optional. They serve as support or guidance and may be executed when operationally appropriate, but they are not mandatory.
REQUIRED tasks are mandatory. They represent steps that are defined by configuration. REQUIRED tasks remain visible until they are completed or explicitly handled. This classification has no impact on whether a task is executed automatically or manually. It describes only the operational relevance.
When tasks are executed
Tasks can be executed automatically or manually.
Automatic execution
Automatic tasks are triggered whenever Dispatch is clicked in an operation. At that moment, the system checks all tasks that are configured for automatic execution and starts them sequentially in the background. Automatic tasks do not run on every operation change, only on dispatch.
Manual execution
Manual tasks are not started automatically. They appear in the operation and can be triggered manually when needed. Some tasks may be executed only once, others multiple times.
The task lifecycle
Each task follows a defined lifecycle within the operation.
First, the task is created and appears in the operation with the status Available.
When it is started, it moves into a queue and then into In progress.
After completion, it receives either Completed or Failed.
For tasks that wait for an external response, the status remains In progress until a response arrives or a timeout is exceeded.
Task status and meaning
Status | Meaning in the operation |
Available | Task exists but has not been started |
Queued | Task has been triggered and is waiting to run |
In progress | Task is being executed or is waiting for a response |
Completed | Task was executed successfully |
Failed | Task could not be completed successfully |
Not supported | Task cannot be executed in this session |
Tasks with external feedback
Some tasks do not complete immediately but wait for an external confirmation. In these cases, the task is started and remains In progress until a response from a connected system arrives. The response either confirms success or reports an error.
If no response is received within a defined time, the task is automatically marked as Failed, making it visible that the technical step did not succeed.
Repeating tasks
Depending on the operation state, the same task can appear multiple times.
This happens, for example, when a task template applies to multiple matching resources, keywords, or other operation attributes. Each of these situations generates its own task. These tasks look similar but each contains a specific reference, such as to a particular resource. This makes it clear why the task exists. Connected interfaces can use this reference for specific technical behavior.
Order and background execution
Automatic tasks run in the background and are processed sequentially. They do not block work in the dispatch system. Status changes are updated and displayed automatically.