- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have a flow designer in which I am updating the time zone with location.timezone if the location is not empty and trigger condition is Record created or updated.
The flow is currently triggered on Record Created OR Updated, which causes it to run even when the Location field is empty.
As a result, unnecessary entries are being inserted into the sys_flow_context table.
Also, I could see the flow logs twice for the same user record in PROD instance and I couldn't replicate this issue in non-PROD.
When I verified the logs, I found in both logs the if condition also executed and update happens twice. How can be the update happen twice in the same timestamp for a particular user.
What could be the reason for this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
capture this in DEV in update set and test it thoroughly there
Then migrate to TEST and verify it there
Then only migrate to PROD
💡 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 || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
it should trigger on every unique change.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
But this is happening in Test instance and not happening in Dev though it has same flow in both env,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I opened the flow in test instance and activated it manually again without making any changes and this time, it is working and not creating the logs if the location is empty.
Do I need to capture this change again or the existing update set will suffice?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
capture this in DEV in update set and test it thoroughly there
Then migrate to TEST and verify it there
Then only migrate to PROD
💡 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 || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader