A vRealize Orchestrator workflow runs according to a logical flow of events.

When you run a workflow, each schema element in the workflow runs according to the following sequence.

  1. The workflow binds the workflow token variables and input parameters to the input parameters of the schema element.
  2. The schema element runs.
  3. The output parameters of the schema element are copied to the workflow token variables and workflow output parameters.
  4. The workflow token variables and output parameters are stored in the database.
  5. The next schema element starts running.

This sequence repeats for each schema element until the end of the workflow.

Workflow Token Check Points

When a workflow runs, each schema element is a check point. After each schema element runs, vRealize Orchestrator stores workflow token variables in the database, and the next schema element starts running. If the workflow stops unexpectedly, the next time the vRealize Orchestrator server restarts, the currently active schema element runs again, and the workflow continues from the start of the schema element that was running when the interruption occurred. However, vRealize Orchestrator does not implement transaction management or a rollback function.

End of Workflow

The workflow ends if the current active schema element is an end element. After the workflow reaches an end element, other workflows or applications can use the output parameters of the workflow.