In an architecture with a supervisor the event service job chain must run on the supervisor. When using the EventSubmit Job the event will be created with the field value spooler_id=id_of_supervisor in the database. (SPOOLER_ID is the spooler id where the event service is running).
When running the job sos.scheduler.job.JobSchedulerExistsEventJob to check the existing of an event, no events are found. The reason is that the scheduler id of the scheduler instance where the JobSchedulerExistsEventJob runs does not match the scheduler id that is stored in the database.
The workaround to specify the scheduler id in the submit job does not work as when restarting the supervisor, the events will not be restored.
The job must provide the parameter scheduler_event_service_id to specify the scheduler id of the supervisor and use this in the select statememt.
The job sos.scheduler.job.JobSchedulerExistsEventJob should be able to check events that are located on the supervisor job scheduler. To achive this, the job should provide the parameter scheduler_event_service_id
Use the job com.sos.jitl.eventing.checkevents.JobSchedulerCheckEventsJSAdapterClass This job directly looks into the database and already provides the parameter event_scheduler_id