Question
Evonsys
NL
Last activity: 13 Apr 2022 9:15 EDT
Flow has ended but not removed from pxflow and Assign-Worklist
Hi All,
When user moved from one flow to other flow, previous flow (which is of category ScreenFlow) is not removing from pxflow and Assign-Worklist.
Later, when user returns to the flow(which was not deleted), new flow got created in pxflow and Assign-Worklist (with flowname as XXXX_1). And now, when user opens the assignment , "The flow this assignment corresponds to is no longer at this task;" message is getting displayed.
We checked logs and didn't found any clue. Unable to reproduce these scenarios. And this issue is not happening always.
What could be the root cause of this issue?
Thanks,
Jeevitha
***Edited by Moderator Marije to add Capability tags***
Accepted Solution
Updated: 13 Apr 2022 9:15 EDT
Pegasystems Inc.
GB
The "Error:Flow Removed" and "Error:Flow Not At Task" errors errors occur when you open an assignment and the assignment doesn't match any page on the work object's pxFlow page. This usually means you have a data integrity issue. Either a stale version of the work object or the assignment was written to the database, overwriting the correct version. This usually happens when there is a manual commit added (or an inappropriate Obj-Save with Write Now selected). I would start by looking at the work object history of the items in this state to see if there is a common path through the flow that gets them into this state. Then I'd trace that and look for commits or saves in your custom code
Are you using the Change Stage utility when moving one flow to other flow?
Once the flow is finished, the pxFlow page should be removed.
Are you using any of the below?
Startnewflow -Starts an additional flow execution on the current work item.
Startflow -The standard Start a New Flow on the Object (StartFlow ) activity checks if each of the flow's required parameters are present, as well as run the flow catching all exceptions.
The "Error:Flow Removed" and "Error:Flow Not At Task" errors errors occur when you open an assignment and the assignment doesn't match any page on the work object's pxFlow page. This usually means you have a data integrity issue. Either a stale version of the work object or the assignment was written to the database, overwriting the correct version. This usually happens when there is a manual commit added (or an inappropriate Obj-Save with Write Now selected). I would start by looking at the work object history of the items in this state to see if there is a common path through the flow that gets them into this state. Then I'd trace that and look for commits or saves in your custom code
Are you using the Change Stage utility when moving one flow to other flow?
Once the flow is finished, the pxFlow page should be removed.
Are you using any of the below?
Startnewflow -Starts an additional flow execution on the current work item.
Startflow -The standard Start a New Flow on the Object (StartFlow ) activity checks if each of the flow's required parameters are present, as well as run the flow catching all exceptions.
Did you already check the steps outlined in this PCC post, this post and this post?
ie
Make sure you don't have any obj-save or obj-delete calls that targets the work object or the assignment page and that also use the "write now" or "immediate" checkmarks to commit the operation.
Also, make sure you don't have any "commit" calls. The core layer will handle committing of your work.
If you have any of the above extra calls, and if the core layer's commit fails for some reason, it will attempt to roll back but will not be able to since your extra commit has already occurred.
As the issue seems to be random this could be a locking issue. What activity are you using for the transfer? What do you see for the assignment handle on the newAssignPage and the pyWorkPage flow page?
Have a look at some suggestions for troubleshooting in this post.
Also some suggestions for troubleshooting:
https://academy.pega.com/topic/resolving-flow-issues-using-problem-flows/v1