Yes, a boolean flag for (3) would be a good option!
In (1), the code snippet from my original question is the code that I execute on my local machine. It is submitted to a queue with an agent that runs with docker. Please, let me know if this is enough to reproduce it.
Thank you for your reply AgitatedDove14 !
For the point 1, here is what is printed out when the task starts execution for the first time
Syncing scheduler Failed deserializing configuration: the JSON object must be str, bytes or bytearray, not NoneTypeHowever, now I see that this actually doesn't break the code, and this exception is ignored. The task is not started in the first run, but this is because of the reasons discussed in the point 3, I assume. Sorry for a false alarm here.
For the point 2, I was thinking of a use case where we have a heavy job to run, which we would like to schedule for a night time on a Saturday, for example, when the server load is low. Or can this be achieved by e.g. scheduling a job for
weekday=saturday, hour=3 ? For the point 3, yes, I think we would expect the execution immediately. For example, if we want a job to run every 15 min, we don't want to wait 15 minutes for the first execution to happen, we want to start straight away, and then repeat every 15 min 🙂
Example coming soon, with docs :)
First that is awesome to hear PanickyFish98 !
Can you send the full exception? You might be on to something...
2. Actually we thought of it, but could not find a use case, can you expand?
3. I'm not sure I follow, do you mean you expect the first execution to happen immediately?
(2) yes weekdays with specific hour should do exactly that:)
(3) yes I see your point, maybe we should add boolean allowing you to run immediately?
Back to (1) , let me see if I can reproduce, anything specific I need to add to the schedule call?