You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2018. It is now read-only.
Celery processes running as a task via Windows Task Scheduler that have been created by the ebagis.bat install tool stop execution after 3 days, per the Task Scheduler default.
It appears that this default cannot be changed with any flags or options available via the schtasks command. Perhaps the most valid solution is to do something similar to the idea presented in this TechNet thread. That is, schtasks can read a task xml file, which has this setting contained within it. One thought is to create a task, grab its xml, delete it, then recreate it after modifying the xml appropriately. However, perhaps it makes more sense to have a task xml template and only create the task once, after modifying the template appropriately.
Either way, until this is fixed anyone using the install tool needs to know that they will need to edit the task in Task Scheduler, disabling the setting that stops the task after 3 days.
The text was updated successfully, but these errors were encountered:
Celery processes running as a task via Windows Task Scheduler that have been created by the ebagis.bat install tool stop execution after 3 days, per the Task Scheduler default.
It appears that this default cannot be changed with any flags or options available via the
schtasks
command. Perhaps the most valid solution is to do something similar to the idea presented in this TechNet thread. That is,schtasks
can read a task xml file, which has this setting contained within it. One thought is to create a task, grab its xml, delete it, then recreate it after modifying the xml appropriately. However, perhaps it makes more sense to have a task xml template and only create the task once, after modifying the template appropriately.Either way, until this is fixed anyone using the install tool needs to know that they will need to edit the task in Task Scheduler, disabling the setting that stops the task after 3 days.
The text was updated successfully, but these errors were encountered: