I havent implemented that because we are not able to reproduce the issue in Development environment yet. But issue exist in Production and UAT environments. Still couldnt find the root cause of the issue.
The usecase referred on top was a different one where User is using Obj-Save method with writenow parameter in the activity called through utility shape and the error is thrown. Hence the suggested approach was to deselect the writenow parameter used with Obj-save method.
I am assuming your usecase to also be a different one probably a SR might be required to further look into it.
I looked into the SR for you and here's what I found in the Resolution: Issue was because of using the Writenow parameter with Obj-Save. It was resolved after deselecting the writenow parameter used with Obj-save method.
What exactly is the error you are facing? The above SR was for this error message: Error: Flow Not At Task
If you are unable to find more information on PDN to resolve this, I'd recommend that you create a new post for a focussed troubleshooting. To do that, click Write a Post button on the right pane above!