if condition not run in flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2024 03:55 AM
facing an issue in flow designer.
Step 6 : look up records (used to get count of records)
Step 7 : if condition is placed. When count for step 6 is more than 0 then should be evaluated as True.
But in this instance, step 6 is completed but step 7 is not run. Anybody have an idea why this might have happened?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2024 05:36 AM
What happens if you make step 7 count is not 0? It is weird though, since step 7 wasn't even triggered.
Do you have an 'else' in there that did run? Did anything happen after your look up?
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2024 04:04 AM
Yeah, found it us weird. This has happened in only for a couple of executions.
Don't have an else block. It's just stopped after the 6th step.
The flow status was set as waiting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2024 05:25 AM
Did the 'count is not 0' help? We recently found out that we were checking on something being empty and even though the field we were checking indeed was empty, the flow was evaluating it as 'field=empty', so that evaluation step itself wasn't empty. It contained 'field = empty'...
I love flows, but I hate them.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2024 06:14 AM
Didnt change the logic as of now .... As only a couple of executions are affected.
Just trying to identify the root cause for this, so that i can prevent further issues...
In our case the evaluations itself didnt have happen... Probably should check in patch notes if any bugs were resolved by Servicenow side for this particular issue.