I have a workflow running on a choice column, and have set it to start on modified based on whether the column changes from its previous value. When I change the selection in the column, it does not fire.
To try to determine why that was, I changed to on modified condition "yes" then changed the the selection in the column and the workflow fired.
Any idea on why it would work for "yes" on a modified condition but not a "compare previous" condition?
If it matters; the workflow begins with a switch action.
I had a similar question to yours a while back.
Have a look at the following question and answers - How to fire a workflow only when an item is modified
This might help you
Hello email@example.com -
In your workflow settings, look at 'Start when items are modified', and set that to 'Conditional'.
In your conditions, you can evaluate previous values like so:
This will cause the workflow to trigger when the item is modified AND (more specifically) the status has changed.
Hope this helps!
This is exactly how I had it set up. It does not work, the workflow will not start with that condition set.
It will however work when I only select "Yes" for it to run when modified.
Ah ok, missed the site workflow piece of it.
I tested it where the list choice column is updated by a site workflow and it did run the list workflow upon update.
There was a delay, only because the way timer jobs run, but it did fire eventually.
Can you confirm that list item is being updated properly and as expected?
I did see "starting" in the workflow column after the site wf updated the item:
Yes, the site workflow is updating the list properly. I have even tried manually changing choices as well.
The workflow that has the condition start does not even show as starting or anything for me
Hmmm...Not sure without diving into what you have setup already, and to confirm, you are attempting to use a site workflow to update a list item, which then triggers a list workflow, correct?
I would create a new workflow on the same list and make sure that it is behaving as intended.
Set the "start on modified" conditionally and test it to make sure its working.
I have seen in the past strange behavior and had to start over from scratch and it cleared up issues.