Flow to rollback changes if status != Draft. Why is this automation running even when the filter condition should fail?

[Thaha]

I’m trying to prevent edits to fee payment records that are not in "Draft" status.

So I set a filter:

If Previous Status is not Draft → then run rollback.

In this case, the previous status is clearly “Draft” (see console log), so the filter should NOT pass and the flow should not proceed.

But the automation still runs and updates the record.

Is there something wrong with how I’m using the “Previous Value” filter?

I’ve added comments to the screenshot to explain my setup.

Any help understanding this behavior would be appreciated!

[jacquelynmay]

That does seem like it shouldn’t be running based on your logs. Maybe a couple of things you can try:

• Use a script filter to see if that will work
• Use the current value instead of previous value (but in this case, it wouldn’t handle a scenario where someone changes the Status from something else to Draft)

Curious to hear if you find a resolution or whether it’s something going wrong with the “Is not” filter in your flow.

[Thaha]

Thanks, @jacquelynmay. I will try with script filter.
I can’t use the current value for the reason you have mentioned.

Feels like a bug to me.

[Jason]

@Thaha

I got it working (I think) however the not with the Filter as you had it I had to move to a conditional block:

So you have a work round but I would have thought it should work the way you had it.

[Thaha]

This works. It also runs the automation that one time when I change from Draft to Confirmed.

It shouldn’t work. But it does. Any ideas as to how to not allow that to happen.

I don’t see an issue with my logic. Do you think its a filter bug?

[Jason]

easiest way to stop it running on status change would be:

So only have it trigger on fields that are not the status.

Yes I think its a bug I would have expected the way you are doing it to work, I expect that it is not looking at the previous value properly as the filter happens before you have collected the previous values.

[Thaha]

That won’t work as if someone changes a confirmed item to Draft. It won’t run.

I might have to live with this one extra automation run for now, I think.