Hi, I've looked some more into the notification issues I'm having. I created a new user using the modified workflow where the generateToken class is used. As an admin I approved the first step and see the user is in the "created" state. There is a notification attached to this state for users assigned in a certain role. I can find the users in About state using users->search.
In the core log I see: 09:38:00.001 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: scheduler_QuartzSchedulerThread 09:38:00.002 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is being obtained: scheduler_QuartzSchedulerThread 09:38:00.002 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' given to: scheduler_QuartzSchedulerThread 09:38:00.010 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' returned by: scheduler_QuartzSchedulerThread 09:38:00.012 DEBUG org.quartz.core.JobRunShell - Calling execute on job DEFAULT.taskNotificationJob 09:38:04.811 DEBUG org.apache.syncope.core.scheduling.NotificationJob - Waking up... 09:38:04.812 DEBUG org.apache.syncope.core.scheduling.NotificationJob - Sleeping again... 09:38:04.814 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: scheduler_Worker-5 09:38:04.814 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is being obtained: scheduler_Worker-5 09:38:04.814 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' given to: scheduler_Worker-5 09:38:04.823 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' returned by: scheduler_Worker-5 It seems that the job is started but doesn't do anything. Any next steps to investigate? regards Bob
