<story><title>Red Engine: modern scheduling framework for Python applications</title><url>https://red-engine.readthedocs.io/en/stable/index.html</url></story><parent_chain><item><author>dr_kiszonka</author><text>Would you have a recommendation for an easy to use Python scheduler with such a feature for a personal project?</text></item><item><author>mplewis</author><text>Other schedulers have a durable database of attempted runs. This doesn&amp;#x27;t seem to have anything like that.</text></item><item><author>angrais</author><text>If it took less than 5 minutes to boot then I can&amp;#x27;t see why it wouldn&amp;#x27;t work.&lt;p&gt;How would that work for other schedulers? Also, if a server reboots that&amp;#x27;s quite bad all round anyway. Hopefully you&amp;#x27;d be notified directly.</text></item><item><author>wmichelin</author><text>How does it handle state and restarts? What happens if a job is scheduled to run &amp;quot;before 10am&amp;quot;, then the entire server restarts at 9:55am, will it try to run that same job again when it boots back up?</text></item></parent_chain><comment><author>lobocinza</author><text>I think you can create ephemeral timers with Systemd if you&amp;#x27;re on Linux.</text></comment>
<story><title>Red Engine: modern scheduling framework for Python applications</title><url>https://red-engine.readthedocs.io/en/stable/index.html</url></story><parent_chain><item><author>dr_kiszonka</author><text>Would you have a recommendation for an easy to use Python scheduler with such a feature for a personal project?</text></item><item><author>mplewis</author><text>Other schedulers have a durable database of attempted runs. This doesn&amp;#x27;t seem to have anything like that.</text></item><item><author>angrais</author><text>If it took less than 5 minutes to boot then I can&amp;#x27;t see why it wouldn&amp;#x27;t work.&lt;p&gt;How would that work for other schedulers? Also, if a server reboots that&amp;#x27;s quite bad all round anyway. Hopefully you&amp;#x27;d be notified directly.</text></item><item><author>wmichelin</author><text>How does it handle state and restarts? What happens if a job is scheduled to run &amp;quot;before 10am&amp;quot;, then the entire server restarts at 9:55am, will it try to run that same job again when it boots back up?</text></item></parent_chain><comment><author>MonkeyMalarky</author><text>Seconding this. I would love a middle tier job scheduler &amp;#x2F; manager for Python that has persistence. I feel like there&amp;#x27;s a missing middle between cron+scripts and the enterprise grade tooling built for ETL tasks.</text></comment>