Workflow Statuses

• (RE 2.14) Scheduled workflows display on the Workflow Status page. Scheduled has been added as a search filter option.

• (RE 2.14) The Workflow Status page displays a workflow's priority value so that users understand which work is most important and when a particular workflow will start executing.

• Abandoned
  • This status means that it is no longer taking up any resources or compute processes from Reach Engine.
  • Abandoned is a final state status and will routinely get cleaned out by the workflow cleanup process.
  • Abandoned statuses are only assigned by user interaction, it usually indicating a workflow that was kicked off by mistake or one that had a broken process and was abandoned and retried on a different attempt.

• Completed
  • This status means that it is no longer taking up any resources or compute processes from Reach Engine.
  • Completed is a final state status and will routinely get cleaned out by the workflow cleanup process.
  • Completed statuses are what you hope to see in your system, they are the signal that work is correctly being processed on your system.

• Created
  • This status is an active state status and workflows in it are being worked on by Reach Engine processes.
  • Created is the second status a workflow will typically go through after Scheduled status.
  • This is typically a quick a state for each workflow as it quickly moves onto either Queued or Executing depending on available resources.

• Executing
  • This status is an active state status and workflows in it are being worked on by Reach Engine processes.
  • Executing status is showing that the workflow is running and getting the work done it was assigned.
  • Workflows in this status can be Paused or Abandoned.

• Failed
  • This status means that it is no longer taking up any resources or compute processes from Reach Engine.
  • Failed is a final state status and will routinely get cleaned out by the workflow cleanup process.
  • Failed status shows planned failures in a workflow process. This means there are errors written explicitly in the workflow that will use this status if that problem occurs.
  • A user or admin should explore Failed status, find the error message on the failed step, and use the info in that error to correct the issue and then kick off a new job to retry the workflow.

• Paused
  • This status is an active state status and workflows in it are being held onto by Reach Engine processes.
  • Workflows in this status can be Resumed or Abandoned.
  • Paused workflows are typically there because:
    • A user/admin may want to delay the work from finishing.
    • A user/admin may want to pause a number of jobs to free up space in Executing status so that priority workflow may finish first.
    • A user/admin mistakenly started the job and realized they needed make adjustments so they paused the job before finishing and likely will move to Abandon it next.

• Queued
  • This status is an active state status and workflows in it are being held onto by Reach Engine processes.
  • Queued status shows the workflows that are waiting for available queue space and resources to go into Executing status and finish their work.

• Scheduled
  • This status is an active state status and workflows in it are being held onto by Reach Engine processes.
  • Scheduled status shows workflows that have been kicked off and put onto the Scheduler service but have not yet been picked up by a Workflow Runtime service to begin their process.
  • Optional priority values that can be set on workflows will ONLY affect Scheduled status workflows. The priority values will dictate which workflows come off the Scheduler and into a Runtime first, after that priority is no longer applied and its first come first serve.

• Stalled
  • This status is an active state status and workflows in it are being held onto by Reach Engine processes.
  • Workflows in this status can be Resumed or Abandoned.
  • Stalled status will routinely get cleaned out by the workflow cleanup process.
  • Stalled status signify that workflow encountered an error that it did not anticipate. Meaning the workflow does not have a Fail step written into it to account for the error the workflow had. Next steps are still similar to Failed scenario where the user/admin should explore Stalled status, find the error message on the Stalled step, and use the info in that error to correct the issue and then kick off a new job to retry the workflow or reach out to the Reach Engine Support Team if further assistance is needed.