Wonderful, thanks Dave! This is probably the correct approach for me to
take.
And that is a fair point, I think for the most part I organised it like
that to prevent drift (though I do know of the preventdrift argument to
schedule_task()) and ensure that the task always queued for 2200 the
On Monday, September 2, 2019 at 8:23:57 AM UTC-7, Francis Windram wrote:
>
> Hi All,
>
> Seems like a simple question here but I am struggling with finding an
> elegant solution.
>
> I have a scheduler running with one task that runs at around 2200 every
> night, then queues the next run at 2200
On Monday, September 2, 2019 at 8:23:57 AM UTC-7, Francis Windram wrote:
>
> Hi All,
>
> Seems like a simple question here but I am struggling with finding an
> elegant solution.
>
> I have a scheduler running with one task that runs at around 2200 every
> night, then queues the next run at
3 matches
Mail list logo