...
- One of the orders could be generated when the job returns 0 and the original job chain would processing at the next_state.
- The other order could be generated when the job returns a specific non-zero code such as 1.
- This code would then be seen as an error and per default cause processing of the original job chain to revert to the error state.
- The non-zero return code could however be used to specify a to_state parameter for the original job chain. This would ensure that processing of the original job chain could continue from a state (i.e. job) specified for the to_state parameter.
References
- The Knowledge Base Articles on Exit Code handling:
- JobScheduler Reference Documentation:
...