Details
-
Feature
-
Status: Dismissed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
- Current Situation
- There is no way to determine if an order has an error or not. There is no error object available at order level. The information is available at task level.
- Desired Behavior
- If within a job chain an API job raises an exception and stop_on_error="false" has been set, then the exception text is stored in a new order object property. The API for orders is extended for that property.
- In case of errors of shell jobs this property stores the message "Task ended with exit code ..." if the order is configured to proceed to the error_state.
- The order property that contains the exception message
- is stored to the database table SCHEDULER_ORDER_HISTORY
- is provided when using an XML API command <show_history ...>
- is provided with the JobScheduler answer to the XML API command <show_state .... The information is provided with a new attribute of the <order> element.
