You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Introduction

  • Orders are triggers for the execution of workflows. They are scheduled for a given date and time. 
  • In addition, orders can carry variables that are available to the nodes and jobs in workflows.

Dashboard Order Summary

Explanations:

  • The Dashboard view shows summary information per order state.
  • Clicking the respective numbers will open the Orders view to display details for orders assigned the given state.

Order States


Error StateDescription
PendingnoOrders are added to workflows and are scheduled for execution with a later date and time
In ProgressnoOrders are processed by a workflow instruction such as Fork but are not running with a job
RunningnoOrders for which a job was started, such orders are waiting for the job to complete
SuspendednoOrders that have been halted on user intervention
CompletednoOrders that finished a workflow but are not automatically removed. 
WaitingnoOrders that wait for a resource such as an Agent or a lock
BlockedyesOrders that cannot start, e.g. due to a failed initial workflow instruction
FailedyesOrders for which a job failed or that have been halted with the Fail workflow instruction. 

For details and a state transition diagram see JS7 - Order State Transitions

Orders View


  • No labels