- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2022 06:26 AM
I am curious if there is a way to bypass a flow wait for duration step. in this case the default wait period is 14 days, but I am needing to adjust that time so that the timer waits for 3 days. This is for adjusting a flow that is currently executing.
Solved! Go to Solution.
- Labels:
-
flow designer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2022 07:30 AM
Hi,
Wait for duration steps just add a future dated trigger. you can view the sys_trigger table for flow.fire records

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2022 07:28 AM
Hi
I don't believe its possible to adjust the run time values in a flow that is currently executing (unfortunately)
This was also confirmed to me by the following article where the user had a similar question and opened a case with ServiceNow who said it couldn't be done.
''Case opened and closed .. it seems not possible to do any changes to the run-time value which is trigger from request catalog, SN didn't provide me where this information are stored either. Suggestion from SN is to try preventing any foreseeable scenarios and create flow steps according to it .. if else and so on.''
https://community.servicenow.com/community?id=community_question&sys_id=73b5eecfdbc698109e691ea668961924
Please mark my answer as Correct/Helpful based on impact
Regards,
Dan H

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2022 07:30 AM
Hi,
Wait for duration steps just add a future dated trigger. you can view the sys_trigger table for flow.fire records
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2024 04:02 AM
Not sure if something has changed (currently on a Vancouver instance). But in addition to setting the 'Next action' to a historical date on the Trigger [sys_trigger] table, I also found that it was necessary to update the 'Processed' date to historical value on a 'flow.fire' record which is generated on the Event [sysevent] table.