-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
elsa-extensions/src/modules/scheduling/Elsa.Scheduling.Quartz/Jobs/RunWorkflowJob.cs
Line 60 in cf67fd3
| await context.Scheduler.DeleteJob(context.JobDetail.Key, cancellationToken); |
If there is any exception thrown inside the RunWorkflowJob, which could be a transient database failure while loading the workflow definition, the job gets deleted.
This causes the problem that no further jobs are run and no new jobs can be scheduled.
For example, trying to publish a workflow containing a cron trigger will fail with the exception:
Quartz.JobPersistenceException: The job (Default.RunWorkflowJob) referenced by the trigger does not exist.
Currently, the only way to recover from this state is to restart the application, because jobs are recreated only by the startup job.
Maybe this is also the cause of elsa-workflows/elsa-core#7033
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels