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 identify the cause of the failure, similar to an advanced default error handler, and take appropriate action.
Key Requirements
Transferring Information from the Main Workflow
When the main workflow fails (for example, after completing 10 scriptable tasks), it is necessary to extract relevant information from the failed process, including variables, values, and the process state.
It is important to identify which variables have null values so that the fallback can dynamically decide what to do: continue, apply a fix, or execute specific scriptable tasks.
Fallback Operation
The fallback process needs to receive all variable values and state information from the main workflow exactly as they were right before the failure.
The fallback can then analyze these values, make logical decisions, and perform corrective actions or continue processing as needed.
Central Questions and Possible Solutions
How can you extract information and state from the Main workflow?
You should investigate whether mechanisms such as the default error handler can be used to collect and transfer state information.
It is important to understand what vRO 8.18.1 supports in terms of preserving variables prior to crashes or failures.
How do you transfer variable values to the Fallback?
Ensure that all required variables and values are accessible to the fallback process, for example by serializing the state or saving values in advance.
You may need a trigger or interface between the main and fallback workflows to transfer information accurately and efficiently.