- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 07:22 AM
I have a flow that runs monthly on the 1st. I checked the scheduled jobs for that flow, but I cannot find one.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 09:55 AM
When reproducing this (first findings, haven't double cross checked yet):
1. There's a sys_trigger record, which contains a name like: Trigger:e5183ae81b41c5101ab0fcc6cc4bcb96
And job context like:
#Tue Jan 11 09:45:00 PST 2022
fcDocumentClass=sys_flow_trigger_auto_script
fcDocumentKey=ad183ae81b41c5101ab0fcc6cc4bcb96
fcDocumentScope=
fcDocumentName=Trigger\:e5183ae81b41c5101ab0fcc6cc4bcb96
When this record has run, it's not available anymore and a new record is generated with the new next action date.
2. The sys_id mentioned in fcDocumentKey, is the sys_id of a sys_flow_trigger_auto_script record. That records hold also the Run type (daily, monthy, etc) and the time. Plus scripting like:
sn_flow_trigger.FlowTriggerAPI.fireTimerTrigger('e5183ae81b41c5101ab0fcc6cc4bcb96');
3. The sys_id of the script from step 2, is the sys_id of a sys_flow_timer_trigger record. A record where you see the details of when the flow is scheduled, daily, the time, etc..
4. The sys_flow_time_trigger record, is referenced by the sys_flow_trigger_plan record (which I mentioned in my previous reply). The Plan Id fields holds the sys_id of... your scheduled flow.
Kind regards,
Mark
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 08:13 AM
It's my understanding that the scheduled triggers in Flow Designer do not create a sys_trigger entry, but rather run on their own.
Curious, why the interested in looking for a scheduled job?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 08:44 AM
The flow ran twice and when I checked, there was a scheduled job kicking the flow off. I deleted the scheduled job and now the business unit wants me to prove that it won't run twice on Feb 1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 08:53 AM
If you think you've solved and still need to prove it: Can you reproduce this?
For example with the same flow on a dev/test instance?
Or with a different flow?
Or same/different flow, on a different day of the month?
If my answer helped you in any way, please then mark it as helpful.
Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP
---
LinkedIn
Community article, blog, video list
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 08:55 AM
It is an interesting question though, if it wouldn't be in a schedule like table.
Did a quick search and saw this table which looks interesting:
sys_flow_trigger_plan
Will look into a bit more, sounds like just a good topic to know more about.
Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP
---
LinkedIn
Community article, blog, video list
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
