Fallback workflow - take Variables from main workflow

[kuku Forever]

My system uses vRO version 8.18.1 to manage a central Main workflow that handles highly complex processes. To provide backup and support in case of failures, I want to create a Fallback workflow-an alternative process that will be triggered if the main workflow fails. The goal is for the fallback to precisely detect what caused the failure, similar to an advanced Default error handler, and take appropriate action.

Key Requirements

1. Transferring Information from the Main Workflow:
   • When the main workflow fails (for example, after completing 10 Scriptable tasks), it's necessary to extract relevant information from the failed process: variables, values, and process state.
   • It's important to identify which variables received a null value so that the fallback can dynamically decide what to do: continue, perform a fix, or execute specific Scriptable tasks.
2. Fallback Operation:
   • The fallback process needs to receive all variable values and state information from the main workflow as they were right before the failure.
   • The fallback can analyze these values, make logical decisions, and perform corrective actions or continue working as needed.

Central Questions and Possible Solutions

• How can you extract information and state from the Main workflow?
  • You should investigate whether mechanisms like the Default error handler can be used to collect and transfer state information.
  • It's important to understand what vRO 8.18.1 allows in terms of preserving variables prior to crashes or failures.
• How do you transfer variable values to the Fallback?
  • Ensure all required variables and values are accessible to the fallback process, for example by serializing the state or pre-saving values.
  • You may need a trigger/interface between the Main and Fallback workflows to transfer information accurately and efficiently.