Event not processed: event queue entry remains unhandled

No matching event registration exists in the sysevent_register table for the event name, or the registration record is inactive or has incorrect filter conditions. (high likelihood)

The event processor service is paused or disabled, preventing all event queue processing from occurring across the instance. (medium likelihood)

A script error or exception occurs within the event registration script or notification rule handler, causing the processing to fail silently. (high likelihood)

The event record in sysevent table has malformed or missing required field values such as event_name, table, or sys_id that prevent proper matching. (medium likelihood)

Database locks or performance issues prevent the event processor from accessing or updating the event queue records within the timeout period. (low likelihood)

Step 1: Navigate to System Diagnostics > Log > Application Log and search for the specific event name to identify which event is failing and review any accompanying error messages.

Step 2: Check the Event Queue at System Policy > Events > Event Queue to locate unprocessed events and verify the event name, table, and processing state.

Step 3: Query the Event Registry table at System Policy > Events > Registry to confirm an active registration exists for the failing event name with correct filter conditions.

Step 4: Verify the event processor is running by checking System Diagnostics > Event Management > Event Processor Status or the system property 'glide.events.max_threads' is greater than 0.

Step 5: Test the event registration script by navigating to the specific registration record and using the Test button, or manually trigger the event using gs.eventQueue() in a background script.

Step 6: Review notification rules in System Notification > Email > Notifications if the event should trigger notifications, ensuring the When to send conditions match the event data.

Step 7: Check for script errors in the event handler by adding logging statements or running the registration script in Scripts - Background with sample event data.

Step 8: If performance is suspected, monitor the Event Queue processing rate and consider increasing the glide.events.max_threads system property or reviewing database performance metrics.