How to set the AppScheduler misfire_grace_time parameter in stackstorm ? #5824
Replies: 4 comments 1 reply
-
Here are the details of the technical environnement: StackStorm Version |
Beta Was this translation helpful? Give feedback.
-
This is the same issue as #5831 |
Beta Was this translation helpful? Give feedback.
-
For now, just scheduling the task at a different time has solved the issue. this is clearly related to some VM-Host load. |
Beta Was this translation helpful? Give feedback.
-
HI Team I am also facing this issue . Here are my environment details st2 3.7.0, on Python 3.6.9 |
Beta Was this translation helpful? Give feedback.
-
On one stackstorm installation I've got missing CronTimer events.
In the log I get these kind of entries:
stackstorm st2timersengine[27662]: 2022-11-27 20:45:02,381 WARNING [-] Run time of job "St2Timer._emit_trigger_instance (trigger: cron[hour='20', minute='45'], next run at: 2022-11-28 20:45:00 UTC)" was missed by 0:00:02.381851
After a little Googling, I think I need to set the misfire_grace_time parameter of the AppScheduler component used by Stackstorm.
Howerver I see no such option in the timersengine section of st2.conf, nor in the rule definition for the core.st2.CronTimer trigger.
Can someone point me to the correct way to set this parameter ?
Beta Was this translation helpful? Give feedback.
All reactions