Symptoms
In the administration area or the dispatch center summary, the following error message is displayed:
No task is configured for the simulated dispatching. No or not all resources can be alerted in a simulation. See XENBIT Note #1000000.
In addition, the following effects may occur:
The operation can be dispatched, but resources do not react correctly to dispatching or operation cancellation.
SIM Dispatcher behaves incompletely or inconsistently during simulated dispatch processes.
Cause
One or more mandatory standard tasks required for SIM Dispatcher are missing in the command center. Internally, the system checks during startup and operation whether the following task templates are present:
A task for simulated dispatching of resources
A task for simulated abort of all resources
If one of these tasks is missing or incorrectly configured, SIM Dispatcher cannot execute its core functionality correctly.
Especially relevant is the following: The tasks must have a specific technical implementation, defined conditions, and fixed properties. If these tasks were deleted, modified, or never created, the internal validation fails.
Solution
Option 1: Import the standard configuration (recommended)
The recommended standard configuration provided by XENBIT can be imported directly using YAML.
Simulated Dispatch
description: Transmit Dispatch Data
isMandatory: true
execution: AutomaticOnceThenManualMultiple
createTaskForEachMatch: true
requiresSuccessfulSignal: true
timeoutSeconds: 30
conditions:
- field: UnitId
operator: true
implementationName: XENBIT.ResQueServe.Shared.Executables.SimulatedDispatchExecutable
Simulated Operation Abort
description: Dispatch Cancel to all Resources
execution: ManualMultiple
requiresSuccessfulSignal: true
timeoutSeconds: 30
conditions: []
implementationName: XENBIT.ResQueServe.Shared.Executables.SimulatedDispatchAbortExecutable
Option 2: Manual creation of the tasks
Alternatively, the tasks can be created manually. The following settings must be functionally equivalent.
The name, CAN or MUST classification, and execution type may differ, but are recommended.
Task: Simulated Dispatch
Setting | Value |
Description | Transmit operation data |
CAN / MUST | MUST |
Execution type | Automatic once, then manual multiple |
Multiple creation | Enabled |
External success confirmation | Enabled |
Timeout | 30 seconds |
Condition | Resource ID – Always true |
Technical implementation | SimulatedDispatchExecutable |
Task: Simulated Operation Abort
Setting | Value |
Description | Abort operation for all resources |
CAN / MUST | Optional |
Execution type | Manual multiple |
Multiple creation | Not required |
External success confirmation | Enabled |
Timeout | 30 seconds |
Conditions | None |
Technical implementation | SimulatedDispatchAbortExecutable |
Workaround
There is no technical workaround. Without these tasks, SIM Dispatcher cannot simulate correctly, as dispatching and operation aborts are not processed by the system.
Prevention / Notes
These two tasks are a fixed part of the SIM Dispatcher core concept. They control:
Simulated dispatching of individual resources,
Realistic time-based departure of units,
Simulated operation abort including status feedback.
Important for administrators: These tasks are not optional examples, but mandatory operational standards. They must not be deleted or functionally modified if the command center is intended to operate with SIM Dispatcher. Adjustments should only be made in copies, not in the original tasks.
Recommendation: The standard tasks should be clearly documented and protected against modification. If problems occur with dispatching or operation abort, always verify first that these two tasks are present and correctly configured.