Posted: 6 Jan 2020 23:26 EST Last activity: 7 Jan 2020 5:31 EST
The flow this assignment corresponds to is no longer at this task
Randomly we are seeing this error 'The flow this assignment corresponds to is no longer at this task.'
I have gone through similar posts to figure out the root cause but to no avail. We are not using explicit commit, our SLA just updates the urgency nothing else so no question of SLA triggering any processing and more ever we have optimistic locking configured.
In terms of mismatch between newAssignPage and pxFlow(), yes there is. In our case, all affected assignments have have just 2 properties in the corresponding pyWorkPage.pxFlow() - pxObjClass and pxSubscript.
Any idea why other properties are not populated in the pxFlow() page or what could be the problem?
we faced something similar in one of our project and the root cause for it was stale workobject due to optimistic locking. 2 users updated the same workobject causing newAssignPage and pxFlow page data to differ.
we fixed the issue at our end by doing some customization to force user to close the workobject if its stale.