We observed that the sendCorr Agent is updating the case in the background because of which user is getting the resubmit issue.
This issue occurs when we use below steps in the flow.
1) Send email smart shape to send email
2) Assignment shape for user action. (here the SendCorr Agent runs in the background and updates the case which will give the resubmit issue for the user)
As identified, sendcorr agent runs and gets the lock on work object and save to update correspondence sent time and few other details like whether workparty notified or not in pyworkPage.pyWorkParty(PartyRole).pyPartyNotified property. And this issues happens only in case of optimistic locking.
We gave the below Local change for the above issue:
SendCorr agent activity 'Send' which internally calls OnSend activity, can be overridden at application layer and in class Data-Corr-Email. Then you can skip the steps conditionally to update the work properties if its optimistic locking and if you are not relying on these properties like pyPartyNotified and correspondence sent time.