Create record action in flow designer trigger before business rule

[trangdan106]

Hello everyone, I have a flow where I will create a case, I also have a before business rule which runs on said table but for update operations. The business rule has a filter condition of the "priority changes".

I've noticed that my business rule will triggered when my flow created the case record. I have also created another test flow which run on update and has the same condition has the business rule, it too gives the same result as the business rule:

Have anyone seen this problem before?

[Ankur Bawiskar]

@trangdan106 

my thoughts

-> The "changes" condition evaluates true on insert when a field transitions from null → value.
-> From the screenshot, it looks like priority changed from null to 3 - Moderate, which is why it appears in changed_fields.
-> Flow Designer treats the initial population of a field during record creation as a change.

things to check

-> If the Business Rule is configured for Update only, check whether an additional update is occurring immediately after the record is created.
-> To confirm, log current.operation() in the Business Rule and review the record history/audit entries.
-> If the requirement is to react only to changes on existing records, add logic to exclude cases where the previous value is empty/null.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar]

@trangdan106 

Just following up to see whether my suggested solution worked for you.

If you're still facing any issues, I'd be happy to help further.

[ajmalmuhamm]

Hey @trangdan106 ,

Yes, this can happen, and the key point is that Flow Designer and Business Rules are evaluating the record during the same server-side transaction.

If your Before Business Rule has:

• When = Before
• Update = checked
• Condition = Priority changes

then you should normally expect it to run only when the existing record's priority changes.

However, when the Flow creates the Case, check whether the priority is being populated/changed as part of the same transaction. Also check whether another Business Rule, Flow action, Data Policy, or other automation subsequently updates the Case after creation. That second update can satisfy the "Priority changes" condition.

For Flow Designer, an Updated record trigger with a condition such as Priority changes is also capable of triggering when that field changes. ServiceNow documents that Updated triggers evaluate changes to non-system fields.

I'd recommend checking the Case → History and Flow execution details for the exact sequence:

Create Case → Priority populated/changed → Case updated → BR/Flow triggered

Also verify that the priority isn't being set immediately after creation by another step in your Flow. This is a common reason it appears that an Update condition is firing during creation.

If you want to guarantee that the Business Rule never executes during insert, you can also explicitly protect it:

if (current.operation() != 'update')
    return;

Then keep your existing priority-change condition.

This is especially useful as a defensive check, although I would first identify what is actually updating Priority after the Case is created, because that is likely the underlying cause.