I have a list Workflow that has two web requests, at the beginning and the end of the workflow. The web requests triggers a flag in an external database. The idea is that when the workflow starts, the flag is set to 'active', and once the workflow is about to end the flag is then set to 'inactive'. I use this flag so that I can notify users in an external application whether there is a workflow currently running.
The problem is, I've noticed that users sometimes manually cancel workflows when they're no longer relevant to them. This causes the flag to get stuck on 'active' since the end of the workflow is never reached and the last web request never fires.
Is there any way to set an action that can still fire after a workflow has been canceled? Or perhaps have another workflow that monitors the first, and then sends a web request when it sees that it's been canceled?
Any help is greatly appreciated!
You can create workflow where the status would be actual worklow status equal to cancelled, then this workflow should kick off and set the action to update inactive.
Thank you for your advice,
I tried what you suggested but I am having trouble checking the status of the first workflow.
I'm using a "Wait for item update" action to check the workflow status column, like this:
Unfortunately, this does not work. This new workflow never recognizes that the status of the first is now set to 'Canceled'. Can you see something that I may be missing here?
workflow statuses are represented by their numeric value