Strange Timer issue

Hello,
I got a strange behavior with a timer.

The following timer is set and properly started at the correct Date and Time:

2019-10-28 11:00:00.003 [DEBUG] [t.internal.actions.TimerExecutionJob] - Executing timer 'DEFAULT.2019-10-28T11:00:00.000+01:00: Proxy for org.eclipse.xtext.xbase.lib.Procedures$Procedure0: [ | {
  <null>.bBewaesserung_Rasen_geplante_Ausfuehrung = <XBooleanLiteralImpl>
  logInfo(<XStringLiteralImpl>,<XStringLiteralImpl>)
  <XFeatureCallImplCustom>.sendCommand(<XFeatureCallImplCustom>)
} ]'
2019-10-28 11:00:00.003 [INFO ] [home.model.script.Bewaesserung Rasen] - >> START! 
2019-10-28 11:10:00.001 [DEBUG] [t.internal.actions.TimerExecutionJob] - Executing timer 'DEFAULT.2019-10-28T11:10:00.000+01:00: Proxy for org.eclipse.xtext.xbase.lib.Procedures$Procedure0: [ | {
  <null>.bBewaesserung_Rasen_geplante_Ausfuehrung = <XBooleanLiteralImpl>
  logInfo(<XStringLiteralImpl>,<XStringLiteralImpl>)
  <XFeatureCallImplCustom>.sendCommand(<XFeatureCallImplCustom>)
} ]'

For unknown reason the same timer is running again, even they should be canceled already.
The strange point is the date when the timer starts. The time does match, however not the day.

As below, the running timer is from a very old test I run on Oct 6th. However it is started today.
The timer always start at the correct time, but seems to ignore the date.

Any idea what is causing this problem?

Is there a way I can list all pending timers?

2019-10-28 16:27:00.016 [DEBUG] [t.internal.actions.TimerExecutionJob] - Executing timer 'DEFAULT.2019-10-06T16:27:00.000+02:00: Proxy for org.eclipse.xtext.xbase.lib.Procedures$Procedure0: [ | {
  <null>.dStartTime = <XMemberFeatureCallImplCustom>
  <null>.dEndTime = <XMemberFeatureCallImplCustom>
  <XFeatureCallImplCustom>.reschedule(<XFeatureCallImplCustom>)
  <XFeatureCallImplCustom>.reschedule(<XFeatureCallImplCustom>)
  <XFeatureCallImplCustom>.sendCommand(<XFeatureCallImplCustom>)
  logInfo(<XStringLiteralImpl>,<XStringLiteralImpl>)
  <null>.bBewaesserung_Rasen_geplante_Ausfuehrung = <XBooleanLiteralImpl>
  <XFeatureCallImplCustom>.sendCommand(<XMemberFeatureCallImplCustom>)
  <XFeatureCallImplCustom>.postUpdate(<XBinaryOperationImplCustom>)
} ]'
2019-10-28 16:27:00.018 [DEBUG] [el.script.internal.actions.TimerImpl] - Scheduling a new job job 'DEFAULT.2019-10-06T16:25:00.000+02:00: Proxy for org.eclipse.xtext.xbase.lib.Procedures$Procedure0: [ | {
  <XFeatureCallImplCustom>.sendCommand(<XFeatureCallImplCustom>)
  logInfo(<XStringLiteralImpl>,<XStringLiteralImpl>)
  <null>.bBewaesserung_Rasen_geplante_Ausfuehrung = <XBooleanLiteralImpl>
} ]' because the original has already run

Unable to comment. Nothing you’ve shown us has anything to suggest any cancelling should be happening.

What are you setting your timers to, to expect a particular date?

Not that the job ID DEFAULT.2019-10-06...etc is derived from the original creation; when you reschedule an existing timer I think this stays the same.

Not so far as I know.