Event Management events stuck in 'Queued.' state.

[Sandeep _1]

What is the solution if events are stuck in the 'Queued.' state?

[Harish Bainsla]

Hi

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0687516#:~:text=-%20For%20the....

[chetanb]

Did you get a chance to check long running transactions on all nodes, slow running queries. 

To find stuck jobs

• Go to this URL
  sys_trigger_list.do?sysparm_query=state=2^ORstate=-1^ORstate=1^ORstate=-2^next_action<javascript&colon;gs.beginningOfLastMonth()^sys_updated_on<javascript&colon;gs.beginningOfLastMonth()^trigger_type!=0^trigger_type!=2^trigger_type!=9^trigger_type!=^parentISEMPTY
• This query finds the stuck jobs which are
• in state Queued or Running or Error
• and, have next_action and sys_updated_on (Updated) before the last month
• and, are not Run Once, On Demand (Disabled), Run at System Startup jobs
• and, are not child jobs (these jobs are managed by the system

Recommendation for Event Processor Jobs
Event Processor jobs can be identified using the job's script. They have script like GlideEventManager(<queue_name>).processDelegatedEvents(); or GlideEventManager(<queue_name>).process();. For example, GlideEventManager('metric_update').process(); is the script for "metric update events process" job. Other examples of event processor jobs are 'report view events process', 'PA clean scores events process'.

1. Go to sysevent list
   2. Search for queue = <queue name> AND state = ready
   You can get the queue name from the event processor job's script. e.g. 'report_view', 'metric_update' 
   3. Check how old are the events, identified by process_on
   CAUTION: Before recovering a stuck event processor job, check if you should delete very old events for the associated queue. Processing huge events can take significant time and resources, and processing very old events can fire obsolete notifications.

To recover a stuck job

1. Go to the sys_trigger record
   2. Change the state to Ready 

This will make job start running again. Please see following recommendation before applying the workaround

[AJ-TechTrek · Accepted solution]

Hi @Sandeep _1 

Refer the below KB article, which help to resolve your issue.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0687516#:~:text=%2D%20For%20t....

Also I didn't say this is a constraint. If you look at Toms post you will see that gs.eventQueue is under this form:

gs.eventQueue("sn_customerservice.DOB_Update_Case_Sched", gr,   gs.getUserID(), gs.getUserName(),gdt);

The function call is done with 5 parameters out of which last argument value is a date object rather than a queue name. In his screenshot you can see queue contains a date rather than either being empty or containing a specific queue.

Here:

https://developer.servicenow.com/app.do#!/training/article/app_store_learnv2_automatingapps_jakarta_...

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ