Hi Everyone,
We are migrating our Pega Sales Automation application from Traditional UI to Constellation on Pega 25.1.3 and hitting an issue with older, in-flight cases.
We restructured the stages on our Sales Automation Lead case type during the migration:
-
Traditional: 2 stages (
Assign→Resolved) -
Constellation: 3 stages (
Create → Assign → Converted)
In Constellation, Add Task and Add Activity are configured as Case-Wide Optional Processes.
-
For new Leads created directly in Constellation: everything works as expected.
-
For old Leads created in Traditional Sales Automation before the migration:
-
When opened in Constellation, the stage chevron bar displays all three stages as “Not started”.
-
Clicking Add Task or Add Activity fails with pyErrorMessage = FlowProblemNoSuchStage AddTask and routes the case directly to pzStageProblems.
-
Old in-flight Leads still carry stage metadata from the previous structure. When the Add Task flow completes, Pega tries to return context back to the parent case’s active stage.
Because the traditional stage setup does not exist in the new stage setup in Constellation, the engine cannot resolve the stage and throws Flow Problem No Such Stage.
What is the best approach to handle these in-flight cases.
Attached: Screenshot 1 - Clean Constellation Lead audit trail with stage movement vs. Screenshot 2 - Traditional Lead audit trail missing stage transition