I'm using Quartz in Spring Boot. The issue arises when there's a loss of connection to the database during job execution. Upon restoring the database connection, the trigger remains in the database with a status of BLOCKED. At that point, restarting the application is necessary to unblock the job or manually change trigger status in the database.
Is it possible to configure Quartz to wait for the database connection to be restored?