Page History
...
- Download (upload .json): pdwOrderOperations.workflow.json
Anchor | ||||
---|---|---|---|---|
|
Orders in PENDING, SCHEDULED, IN PROGRESS, RUNNING, SUSPENDED, PROMPTING, WAITING, BLOCKED and FAILED states can be cancelled: for details see the JS7 - Order State Transitions article:
- Cancel: This operation allows the order to complete the current instruction, for example, executing a job, and after completion of the instruction the order will leave the workflow with a failed history outcome.
- Cancel/Kill Taskforce: The operation kills processing of forcibly terminates the current instruction, for example a running task for a job, and makes the order leave the workflow.
...
- Cancelling an order is performed as an asynchronous operation which includes the JOC Cockpit, Controller and Agent.
- In a first step the order is displayed with a green/red bullet icon indicating that the order still is running and that the cancel operation is in progress.
- If the Controller or Agent cannot be accessed then the display of the order will remain unchanged.
- Note that "inaccessible" can mean that the network connection has been lost and that the Agent in fact is up and running. In this situation the order will continue to be processed by the Agent until the order cancel operation is successfully transmitted to the Agent.
- In a first step the order is displayed with a green/red bullet icon indicating that the order still is running and that the cancel operation is in progress.
Anchor | ||||
---|---|---|---|---|
|
Orders in PENDING, SCHEDULED, IN PROGRESS, RUNNING, PROMPTING, WAITING, BLOCKED states can be suspended:
- Suspend: This operation allows the order to complete the current instruction, for example, executing a job, and after completion of the instruction the order is put to the SUSPENDED state.
- Suspend/Kill Taskforce: The operation kills processing of forcibly terminates the current instruction, for example, a running task, and puts the order in the SUSPENDED state.
...
- Suspending an order is performed as an asynchronous operation which includes the JOC Cockpit, Controller and Agent.
- In a first step the order is displayed with a green/orange bullet icon, indicating that the order still is running and that the suspend operation is in progress.
- If the Controller or Agent cannot be accessible then the display of the order will remain unchanged.
- Note that "inaccessible" can mean that the network connection has been lost and that the Agent in fact is up and running. In this situation the order will continue to be processed by the Agent until the suspend operation is successfully transmitted to the Agent.
- In a second step the order will be displayed with an orange bullet icon indicating that the order has been suspended.
- In a first step the order is displayed with a green/orange bullet icon, indicating that the order still is running and that the suspend operation is in progress.
Anchor | ||||
---|---|---|---|---|
|
FAILED and SUSPENDED orders can be resumed from the Workflows view as follows:
...
- A period shorter than configured with the Cycle Instruction can be specified.
- Periods are specified by relative dates, for example
1h
(1 hour),10m
(10 minutes),01:30:00
(1 hour, 30 minutes). - Specifying a value
0
for the period will cause the order to continue from the resumed position in the workflow, to execute subsequent jobs and to leave the cycle next time it meets the Cycle Instruction.
- Periods are specified by relative dates, for example
- A period that is specified longer than configured with the Cycle Instruction will be ignored
Anchor | ||||
---|---|---|---|---|
|
Orders in a PENDING, SCHEDULED or WAITING state for a JS7 - Cycle Instruction or JS7 - Retry Instruction can be forced to run immediately from the Workflows view as follows:
...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The operation is available with the Workflows view and can be applied in a situation when users find more than one version of the same workflow:
...