My visual Studio sequential workflow has escalation feature enabled, so the workflow will run every 5 minutes and check the task is overdue or not. If it is overdue it will escalate to another user.
My problem is, I made some changes in workflow.xml file and deployed to the server, by mistake I forget to put the closing tag in workflow.xml file. I realized my mistake and redeployed the workflow in two minutes time. The workflow log History start showing
“workflow name failed to run" (this message logs only two time with one minute difference) and the workflow went to sleep (Last run time in the workflow status page is not changing after that).
And the new instances are working perfectly, problem only for old instances.
This problem is affected for more than 400 items.
I would like to know, is there any way we can wake up the workflow and start checking the task is overdue or not.
I have one more issue recently, i had deployed the workflow with the below bat file (this time i made some changes in the code ), suddenly old instances stop working. even it does not wake up when the task status is Approved (if the task is Approved it suppose
to go to next level).
For deploying the workflow, i am just hitting the BAT file. An
View Complete Post