Flow Designer Look Up Record Cannot Find Newly Created alm_license Record
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hello,
I'm troubleshooting an issue in a Flow Designer catalog item and hoping someone may have run into something similar.
I have a software request catalog item that creates a Software Entitlement record (alm_license) through a subflow. The record is being created successfully and I can verify that the Software Entitlement exists.
The issue occurs afterward when I attempt to use a Look Up Record action to retrieve the same alm_license record using the Sys ID returned from the create step.
My flow sequence is:
- Create Software Entitlement (alm_license) record in a subflow.
- Wait 15 seconds.
Create Catalog Task - Submit Catalog Item Request
- Update Requested Item Record
- Use a Look Up Record action on alm_license where:
- Sys ID = Sys ID returned from the create step.
Occasionally, the lookup fails with:
No record found in Look Up Record action
What's confusing is that the Software Entitlement record was successfully created and exists in the instance. I have verified that the created record's Sys ID matches the Sys ID being returned by the create step.
In the flow execution details, the lookup step shows:
Table: alm_license
Condition: sys_id = [Create Software Asset -> Sys ID]
but the lookup still returns no record found.
The reason this is causing issues is that downstream steps use values from the Software Entitlement record (cost, asset tag, display name, etc.) to populate another request, and when the lookup fails those fields remain empty and causes my flow to error.
Has anyone seen a situation where a record is successfully created but an immediate Lookup Record action cannot find it, even after a wait step? Are there any known timing, transaction, or reference output issues with subflows returning record references that could cause this behavior?
Any suggestions would be appreciated.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Is there an obvious pattern when it fails?
From a troubleshooting perspective, if it's only failing occassionally, then my first thought would be that in those instances, the creation of the Software Entltlement record is taking longer than usual and therefore is not available yet when the flow gets to that stage.
Are you able to increase the wait time?
☕ Powered by caffeine, curiosity, and more failed attempts than I'd like to admit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
I haven't been able to identify a consistent pattern when it fails. My initial thought was the same, that the Software Entitlement record might not be available yet when the lookup runs, which is why I added the 15 second wait before the Look Up Record step.
Even with the 15 second wait in place, I've still seen the lookup fail with "No record found in Look Up Record action."
I haven't tried increasing the wait time more than 15 seconds yet, but that is something I can try. Thanks for the suggestion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
I did a quick Google and if you spot this again , you may be able to see how long the transaction took.
Open up Workflow Studio and select the 'Operation's tab and then the 'Flows' tab. Click on a record and you should hopefully see the duration displayed in milliseconds
DISCLAIMER: This solution is brought to you by Google AI 🤖
☕ Powered by caffeine, curiosity, and more failed attempts than I'd like to admit