
- 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 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