Applications that create a large volume of events and/or events that take a long time to process should use a custom queue.
Populate the Queue field for the event in the Event Registry to define a custom queue. Use only lowercase letters, no spaces, and no special characters except underscore (_).
Note : By Default behaviour of Queue
Adding a value to the Queue field creates the custom queue. When the employeeOccasion event is generated, the event is added to my_queue. The events in my_queue are stuck in the queue because there is no process watching the queue for events.
Learning is if you create a event and if you want all your events should trigger via your queue one by one then put a queue and copy a scheduled job which will check events under your queue and trigger it.
To create a process to watch my_queue, COPY the text index events process Scheduled Job.
In the main ServiceNow browser window, use the All menu to open System Scheduler > Scheduled Jobs > Scheduled Jobs.
Locate the text index events process Scheduled Job and open the record for editing.
To create a process to watch my_queue, COPY the text index events process Scheduled Job.
In the main ServiceNow browser window, use the All menu to open System Scheduler > Scheduled Jobs > Scheduled Jobs.
Locate the text index events process Scheduled Job and open the record for editing.
Change the Schedule Item Name and the queue name in the Job context. The queue name passed to GlideEventManager() must be an exact match to the queue name in the Event Registry.
Hope this helps!
Thanks,
Shamma
