Starting a process with a HT with notifications, scheduled in future, a restart will cause timers to register outside GlobalService, causing a duplication when runtime manager for process is created and the deadline is reached:

Enabling logger:

After create the task and restart at deadline it shows:

14:18:10,068 DEBUG [org.jbpm.services.task.deadlines.notifications.impl.NotificationListenerManager] (EJB default - 1) Sending notification org.kie.internal.task.api.model.NotificationEvent@22801779 to Custom listener with params org.jbpm.services.task.identity.DefaultUserInfo@22c841d1

14:18:00,236 DEBUG [org.jbpm.services.task.deadlines.notifications.impl.NotificationListenerManager] (pool-16-thread-1) Sending notification org.kie.internal.task.api.model.NotificationEvent@6fa20529 to Custom listener with params org.jbpm.services.task.identity.DefaultUserInfo@22c841d1

See notification from GlobalTimerService comes from (EJB default - 1) and from ScheduleFuture from (pool-16-thread-1)

Related code:

This code is triggered

https://github.com/kiegroup/jbpm/blob/main/jbpm-human-task/jbpm-human-task-core/src/main/java/org/jbpm/services/task/impl/TaskDeadlinesServiceImpl.java#L91-L126

before timerservice is initialized:

https://github.com/kiegroup/jbpm/blob/main/jbpm-runtime-manager/src/main/java/org/jbpm/runtime/manager/impl/RuntimeManagerFactoryImpl.java#L144