Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Flow not triggering on normal execution but do on test

alowasoh
Tera Contributor

Hello, I create a flow in flow designer but this is not triggering when case is created.

Since we are in HR scope. I created a record producer(create new store)  that will capture variables on the portal and create create a case on the HR case table . That case creation should be the trigger to create tasks to multiple groups because ne store creation involves many group.

The flow has not error and works fine when running a test with an HRC# already created but not when the record producer is actually summited and the HRC ticket is create on the hr case table. 

What am I doing wrong?

the flow is 

trigger: when case is created wit a record producer {create ne store)

1 Create an hr task on the HR task table.

2 and so on

1 ACCEPTED SOLUTION

Laszlo Balla
ServiceNow Employee
ServiceNow Employee

When you run Test from FD it ignores the trigger, so you know the issue is most likely with your trigger, e.g. the conditions are not true when your case gets crated, etc.

Another common mistake in HR is that the flow trigger is set to run on sn_hr_core_case table, which will not work for some COEs that use an extended table of this, e.g. sn_hr_core_case_workforce_admin. In that case, you need to set the trigger to 'Run on current and extended tables' under Advanced Options.

View solution in original post

2 REPLIES 2

Laszlo Balla
ServiceNow Employee
ServiceNow Employee

When you run Test from FD it ignores the trigger, so you know the issue is most likely with your trigger, e.g. the conditions are not true when your case gets crated, etc.

Another common mistake in HR is that the flow trigger is set to run on sn_hr_core_case table, which will not work for some COEs that use an extended table of this, e.g. sn_hr_core_case_workforce_admin. In that case, you need to set the trigger to 'Run on current and extended tables' under Advanced Options.

alowasoh
Tera Contributor

I adjusted the trigger to run on current and extended table. Thank you