Called Flow Recovery Policy (Magic xpi 3.x)
When a flow is invoked by another flow using the Invoke Flow service, the called flow is considered to be a single step in the first flow. Therefore, the called flow has no Recovery policy of its own.
The figure below shows an example flow that describes how this works:
The above flow on the left is called Scan New Order. It has the following attributes:
-
The flow’s Recovery policy is Save Point.
-
The Save Point is defined in the Email New Order step (Step 3).
-
The Call Process Order step (Step 4) calls a new flow. This flow is regarded as one step, no matter how many steps it includes.
The called flow is invoked by the Scan New Order flow. Because of this, it does not have a Recovery policy of its own. If a system crash occurs at any point in the called flow, it is as if the crash occurred during the Call Process Order step (Step 4) in the calling flow.
In this case, the defined Recovery policy for the main flow is executed. The Recovery policy for this flow is Save Point, so the Magic xpi Server looks for the most recent Save Point, which is the Email New Order step (Step 3). Based on the flow’s Recovery policy, Magic xpi will run the flow from that point.
|
Note:
|
Both the calling flow and the called flow execute the Abort Process above. Only after both flows execute the process, is the defined Recovery policy executed.
|
|
