quartz.net trigger is waiting with next fire time in the past

[benoit J]

Hey,

I have a behavior that I don't understand, and I'm able to reproduce it.

I'm scheduling task few minutes the future on my server and shut down the server, when the server goes back up, the task that have been scheduled does not get fired again.
My trigger for this task is a SimpleTrigger with the default misfire-configuration ("SMART_POLICY")
When I look at my DB I see that my task has:

* a TRIGGER_STATE equal to 'WAITING'
* a NEXT_FIRE_TIME in the past compared to server time (several hours so I don't think that's a GMT+X issue)
* a MISFIRE_INSTR equal to 0 (SMART_POLICY if I'm not mistaken)

Here is the SQL call and the response

SELECT TOP 1000 [SCHED_NAME]

      ,[TRIGGER_NAME]

      ,[TRIGGER_GROUP]

      ,[JOB_NAME]

      ,[JOB_GROUP]

      ,[DESCRIPTION]

  ,CAST(NEXT_FIRE_TIME/864000000000.0 - 693595.0 AS DATETIME) as [NEXT_FIRE_TIME_readable]

      ,CAST([PREV_FIRE_TIME]/864000000000.0 - 693595.0 AS DATETIME) as [PREV_FIRE_TIME_readable]

      ,[PRIORITY]

      ,[TRIGGER_STATE]

      ,[TRIGGER_TYPE]

      ,[START_TIME]

      ,[END_TIME]

      ,[CALENDAR_NAME]

      ,[MISFIRE_INSTR]

      ,[JOB_DATA]

  FROM [QRTZ_TRIGGERS]

  WHERE JOB_NAME = 'cdc1fd37-cba7-4e40-8a31-9b2d44355b21'

I'm not seeing much in the logs of the app.
I've got one warning stating:
2019-11-09 00:25:16; Quartz.Impl.AdoJobStore.JobStoreTX; 7200; This scheduler instance (name_of_my_instance) is still active but was recovered by another instance in the cluster.  This may cause inconsistent behavior.

I'm not sure it's related.

Do you have an idea on why this could happen ?