We have a case where we are encountering the following error: “The requested stage to change to is the same as the current stage.”
Could this be resolved using any out-of-the-box (OOTB) functionality, or is there another way to bring the case back to a normal state?
The restart or resume flow will not work in this scenario.
Hey! From my understanding, this happens because Pega doesn’t allow a case to move to the same stage it’s already in. It looks like somewhere in the logic, a stage change is being triggered with the current stage as the target, so Pega throws that error.
In my opinion, a quick fix would be to add a check before changing the stage so it only runs when the target stage is different. If the goal is to re-run the stage, you could try a small workaround like moving the case to a temporary stage and then back. And if this is more of a flow issue, restarting the flow might help instead of changing the stage.
Could you please check if there are any errors in the tracer that will be helpful to pinpoint the exact issue?
Resume Flow - Ideally, it shouldn’t throw any errors if you’re trying to advance the flow at the correct step with the correct flow name.
Actually, a value was missing, which we added and then restarted the flow. In the past, this approach worked as expected; however, in this case, after restarting, the case was pushed back into an error state. The error indicated: “The flowType is not present in the embedded flow page.” While tracing the issue, we identified the specific flow that was missing and added it back using StartNewFlow.
After this change, we started encountering a different error: “The requested stage to change to is the same as the current stage.” Now, whenever we resume or restart the flow, it consistently returns to the same broken state.