When a deactivation request is issued from the Execution Manager (or directly from the Workflow Monitor), different dialogs appear depending on the type of workflow to deactivate.
...
UDRs already in the workflow, will be processed if they can be processed within the time interval set in the Execution Context property ec.shutdown.time
.
The parameter specifies the maximum time in milliseconds that the EC will wait before a real-time workflow stops after a shutdown has been initiated. This is to enable the workflow to stop all input and drain all UDRs in the workflow before stopping.
Info | |||
---|---|---|---|
title | Example - Setting the property ec.shutdown.time
|
Note | |
---|---|
title | Note!The The wait time is initially set to 60 seconds (60000 milliseconds). If this value is set to 0 (zero) all draining is ignored and the workflow will stop immediately. |
The parameter can be changed at any time, but the EC must be restarted before the changes take effect. For further information see the System Administration user guide.
If the workflow is unable to drain the data within the specified time, the workflow still stops and any remaining data in the workflow is lost. If this occurs, a log note is added in the System Log.
...
Batch workflows have two termination possibilities, indicating whether to wait for the End Batch or not. If the batches are large, and the batch is being loaded by the workflow, the Immediate option will terminate the workflow without waiting for the current batch to finish.
Confirmation dialog when batch workflows are deactivated
Stop Type | Description |
---|---|
Batch | Awaits the next End Batch before unloading the workflow, that is, when the current batch is fully processed. |
Immediate | Deactivates the workflow immediately, causing the current batch to be terminated. This may still take a while, but it is still faster than the |
...
Batch termination option. |