Workflow maintenance batch job - cancelling certain workflows after D365 upgrade

(1) Share

Report

Posted on by Techlady

Hello,

Our workflow maintenance batch job runs every Friday at midnight. We have noticed that after a D365 upgrade goes in, when the job runs next, it cancels workflows where due to matching of certain scenarios, the workflow has been re-assigned back to the originator.

As per screen-shot attached, the purchase invoice workflow was assigned back to originator on 12/07/2024. This workflow instance has a limit of 99 days. When the workflow maintenance ran on 19th July, the invoice still stayed assigned to originator. We had D365 upgrade to Production on Saturday 20th July. When the workflow then ran on 26th July 2024, it cancelled this job automatically. Why is it doing so? Is the upgrade somehow changing/resetting time limits? Its difficult to get more examples as we don't know which ones have been cancelled by batch job and which ones by users.