- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2017 09:55 PM
I'm trying to get inbound email actions working - they're stuck in the Inbox and not being processed. I began performing troubleshooting steps shown here: ServiceNow KB: Troubleshooting Inbound Email (KB0520595)
It looks like my instance doesn't have an "events processing" scheduled job (or I can't find it, I'm a ServiceNow beginner). System Diagnostics page shows 2081 events pending:
Could be related to this issue? Event processing does not run at all on Jakarta instance
However I'd rather not reset my instance if I can avoid it.
build: glide-jakarta-05-03-2017__patch0-05-18-2017_05-31-2017_2011
Any ideas?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2017 07:03 AM
Hi Michael,
It's the same issue you pointed to, unfortunately. Sorry for the inconvenience. You can take a backup of your updates, reset the instance and apply the changes back again. Let us know if you need help or if have any other questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2017 03:38 AM
Hi Micheal,
I had this issue with my Jakarta instance as well as there were no records in sys_trigger table. But I imported the records for this table from my Istanbul instance and the events started to process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2017 07:03 AM
Hi Michael,
It's the same issue you pointed to, unfortunately. Sorry for the inconvenience. You can take a backup of your updates, reset the instance and apply the changes back again. Let us know if you need help or if have any other questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2017 03:56 PM
Thanks Aswin and Bharath. I don't have a prod or other instance to import sys_trigger records from, so I'll read up on backups/update sets and reset the instance and import.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-09-2018 08:07 AM
I had the same issue that started for me yesterday. I checked the sys_trigger table and found that the 'events process 1' jobs were all stuck in the "running" state. I switched all 3 to "ready", and it immediately resolved my issue.