...
After adding the event, the order will proceed with the next step and the event will be removed.
The test_event/job chain_example_wait_for_event_db }} job chain has 2 dummy steps and the wait for event step. This step executes the {{test_event/job_event_check_db job to look for the desired event. The difference to to first example is, that this job uses the events database. You can either specify parameters for event_id, event_class and exit_code to test for a specific event or you can specify a condition for the events you are waiting for.
example:
| Code Block |
|---|
class_a.event_1:99 and not (class_b.event2 or class_b.event3)
if the event_1 in class class_a exists with exit_code=99 and event2 and event3 from class_b do not exist, this expression evaluates to true.
|
You also can specify how to handle the existing or not existing of events with the paramters handle_existing_ah1. "error|success" or handle_not_existing_as"error|success"
example
| Code Block |
|---|
handle_existing_as=error will wait until the events do not exist
|
DEP_EVENTS/JobChainB/JobChainB/Remove_End_Event RemoveEvents step node will only be executed if all the successor job node are executed succesfully. If JobChainB needs to be restarted due to error ,the prerequisite event will be present there This step executes the DEP_EVENTS/JobChainB/JobChainB/Remove_End_Event job to delete desired event.
If the event is not raised, the order executes a setback. The wait time between two checks is configured in the delay_order_after_setback definition of the job (and the job chain node).
After adding the event, the order will proceed with the next step and the event will be removed.
The last
Downloads:
- scheduler events - Documentation
...