Flow Designer workflow is not triggering automatically

[akash_birada]

Hi Community,

I have created a Flow Designer workflow that should trigger when a record is created/updated. However, the flow is not executing automatically.

I have verified:

• Flow is published
• Trigger conditions are configured
• User permissions appear correct

What additional troubleshooting steps should I perform to identify the root cause?

Thank you.

[JenniferRah]

Is the flow not running at all? Like you look at the execution details in Flow Designer and it's not triggering? If so, there's something wrong with the trigger. 

If it's running but immediately failing, then there could be a permissions issue. You might try running it as System User to see if that makes a difference. If not, I would need more information on what the trigger is and what the flow is doing.

[Ankur Bawiskar]

@akash_birada 

did you check what's the flow configuration trigger setting in advanced?

Workflow Studio flow trigger types 

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

[Vikram Reddy]

Hello @akash_birada,

Turn on flow execution reporting first, since publish status and trigger conditions looking right doesn't prove the trigger actually fired. Set com.snc.process_flow.reporting.level to On, or scope it to just this flow via the "..." menu, Flow reporting settings, then check the flow's Executions tab.

Two things usually explain a silent no-run there: the trigger condition checks a field that isn't populated yet when the record event fires, or the record arrives via an integration path, like an import through a Transform Map with business rules disabled, that never reaches the trigger engine. Also check the flow's Run As property: if it's set to the triggering user instead of System user, and that user lacks read access, the trigger fails with nothing logged.

References

• Flow execution details
• How to fix ServiceNow Flows not triggering when conditions are met
• Flow with trigger "repeat" set to run as system, however context is created by a user

Thank you,
Vikram Karety
Octigo Solutions INC

[Tanushree Maiti]

Hi @akash_birada 

1.Navigate directly to Flow Designer > Executions and filter by your specific Flow Name.

• Click into the execution log details to see exactly which condition evaluated to false or where the transaction threw

2.Review the Business Rules running on your target table:

• setWorkflow(false): Search your table's script configurations for setWorkflow(false). If an active script executes this line during insertion or modification, the flow trigger engine will never fire.
• current.update(): Look for any Before or After Business Rules containing current.update(). This anti-pattern forces changes mid-transaction, modifying fields so quickly that the record may no longer match your flow's trigger conditions by the time the engine evaluates it

3. If your flow was migrated via an Update Set, the underlying configuration mapping records might be broken. Make a little cosmetic edit to the flow -> save  -> Publish/Activate again to rebuild the missing system mappings locally

4. Validate your trigger logic.