Flow Designer Wait for Condition causing 5-minute delay in Catalog Task creation and SLA impact
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi Team,
I am facing an issue in Flow Designer related to a Wait for Condition activity.
Scenario:
- A request is submitted through an Order Guide.
- One of the catalog item variables is Email Address.
- If the Email Address variable is not empty, the flow enters a Wait for Requested Item Condition step.
- The condition is:
- Email Address is not empty
- Once the Email Address is populated in varaible, the flow proceeds to Create Catalog Task
Issue:
The logic is working correctly, but the Catalog Task is not created immediately after the Email Address is populated. Instead, the task is getting created approximately 5 minutes later.
At the same time:
- SLA is attached to the request immediately after submission.
- Because of the 5-minute delay, the SLA timer is already consuming time before the Catalog Task is created.
- As a result, the SLA appears to have elapsed about 5 minutes more than expected when the Catalog Task is finally generated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
check this blog and the wait for condition will immediately know when the variable is updated and will proceed
this link has approach from Anil lande on how your flow can wait till that variable is updated and once updated/filled, you can break the loop and proceed
How can w use wait for condition in flow designer for variable?
Also an easier solution is shared there in the same above link, below is the image, it will wait till that Variable is empty, once not empty it will proceed
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
