Events processing not working in my instance

michaelcassidy
Mega Contributor

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:

find_real_file.png

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

1 ACCEPTED SOLUTION

Bharath Prathip
ServiceNow Employee
ServiceNow Employee

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.


View solution in original post

5 REPLIES 5

aswinsiddaling2
Kilo Guru

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.


Bharath Prathip
ServiceNow Employee
ServiceNow Employee

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.


michaelcassidy
Mega Contributor

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.


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.