Look up record action in Flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I am trying to use the look up record action in my flow designer for multiple times in a flow, however only the first action is working and remaining ones are not working/not performing.
Please provide reason for this. The look up record is on the sys_user table.
the flow looks like below where there is flow for individual price cap of 100, 250, 500 as shown below, the lookup record works only for the $100 price cap, but not for the others.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @dassan ,
Could you plz share the flow execution context screenshot, why and where it is fail?
also are the $250 & $500 price cap is nested under $100 or each seperate configured.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
The $250 & $ 500 are separate configuration & are not nested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Okay so you must ensure some checks :
- confirm the price cap field's actual value/type on the test record matches what the If condition checks
- open execution context for $250 If it shows completed with no result > the lookup filter (Name is Tri... / Entra Cost Centre...) isn't matching for that record
Could you plz share the executions to debug it..
If my response helped mark as helpful and accept the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Please check the execution logs for your reference.
for the [rice cap field $250
the look up record under this flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Okay I can see there No Logs so it seems that it simply didn't run.
That happens when the triggering record's price cap value did not evaluate to $250 for that condition,
so check the Condition config shown (estimated_monthly_spend... >250), note it's a >250 style condition, not =250.
