@udaykumart16801936 “Error: Flow Removed” shows up when an assignment record still points to a flow that no longer exists on the case (pxFlow page/flow ID missing or ended), so Pega parks a dummy assignment on the worklist. This often happens after wrap-up if your wrap-up subflow ends or changes stage/flow (pxChangeStage, End shape, tickets, or utility) while the current assignment is still open, or if a step/flow name was renamed/removed during a ruleset upgrade. Typical triggers: canceling the parent flow from inside wrap-up, finishing the assignment twice (FinishAssignment + End flow), SLA waking a closed step, or saving Assign- records with custom code. Fixes: don’t Obj-Delete/Obj-Save assignments; use pxCompleteAssignment then end/transition; if you end a flow, check “remove open assignments” and keep wrap-up in the same flow thread. Preventive: avoid refactoring or deleting steps/flows with in-flight items; if you must, migrate cases first or keep a compatibility subflow. Cleanup: use the Reconcile Work/Worklists utility (admin landing page) to purge orphan “Flow Removed” items, or run the out-of-the-box reconcile activity in lower envs first; as a last resort, bulk remove these assignments only after verifying the cases are resolved or have a valid active flow.