So it’s my understanding of how the
sys_trigger “process events”
works, also known as the event processor.
Frequently it wakes a Java process that reads the
It looks for events which have no named queue where the process date is in the past which have no “claimed by” yet and are in a state of ready. It orders by “process on” and limits to 100 at a time.
So the 100 “oldest” unprocessed events are claimed and a worker start going through them sequenctially. As they are completed, the state changes. When all 100 are done, the thread goes back to slep and waits to be woken again by the scheduled job.
Now there are multiple “process event” records. You can also write your own. This community post goes over the things you need;
These sys_trigger records are ephemeral it seems, one runs and it spawns another and the old one is deleted
- Trigger the event server-side with a queue;
- Insert a new record as a copy of the original “events process” job
where you modify the script from