Job 'Events process 0' taking a long time to restartIssue The purpose of this KB is to fix issues with events not being processed in a reasonable time due to the "Events Process 0" job not running.CauseToo many (+100K) ASYNC jobs on SYS_TRIGGER (which could happen during a database contention issue) impacting the job queue and causing "Events Process 0" job to not run as often as it should.ResolutionGo to SYS_TRIGGER and check how many jobs with names containing "ASYNC." If we have more than 100K jobs like that, mostly likely it is causing the issueFilter by "Events Process 0" job on Name field and add "Parent" column to make it easier to see what jobs should be running (it is ok to have state showing in read for the one which Parent is empty)If all other Events Process 0 jobs are showing "Ready" in red, it is behind the Next Action job and should have already been runningAdd "Priority" column to the view, if it is showing "100" for those jobs, update all of them (including the parent) to "25"You can manually start the jobs by clicking on "Execute Now" from inside the record, after that you can monitor the job using Analyzer (analyzer INST_NAME -W) Once you follow the steps above, the events should be processed fine.