- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2022 09:55 PM
Hi,
After the investigation, I suspect that it is related to the event processor's scheduled job. And I found this scheduled item stuck at the ready state in red colour.
Solved! Go to Solution.
- 5,458 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-07-2022 05:12 PM
I have figured this out, need to change the scheduled item "event process 0" 's next action to a near-future time. And this will be fixed. The scheduled item can be found at System Scheduler >Scheduled Jobs > Scheduled Jobs.
The event processor in the screenshot called "VA Event Processor 0" is not the right one to change.
Hope this can help anyone that has the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-07-2022 05:12 PM
I have figured this out, need to change the scheduled item "event process 0" 's next action to a near-future time. And this will be fixed. The scheduled item can be found at System Scheduler >Scheduled Jobs > Scheduled Jobs.
The event processor in the screenshot called "VA Event Processor 0" is not the right one to change.
Hope this can help anyone that has the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-15-2022 10:13 AM
Thank you very much! I think Servicenow should add this to their KB.
Key words after cloning, event, email, ready, stuck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2022 07:40 AM
I am facing the same issue after my Dev instance is cloned back from Prod (San diego). There is no child "events process 0" exists, only the Parent one with its "Next action" is in the past. It causes all events are stuck in Ready state.
Fixed by changing to near-future time, its children will be created.
I also think this should be included in KB. Any reason why it happened?