Marco Lubian
Marco Lubian
In my opinion, when we're updating a job already scheduled with `upsertJobScheduler`: - by default you could leave the behavior as is: the job scheduling is actually changed, but before...
_The "immediately" flag was removed for the every setting after a lot of deliberation. The rationale is that the most common desired behaviour is that it starts repeating directly from...
> imagine that when you change to 10 minutes, instead of being 14:48:42 it happens to be at exactly 14:50:00 and that the previous job managed to already started to...
Yes, I understand, but the NEW iteration (not the current one) will use the right data and options, right? In that case, let's go on with that change then. One...
Ok @manast. Do you think you could deliver this fix on the next days and for the next PRO version?
Ok, actually that was the second question in fact :-). To me it seems reasonable to act in the way you wrote: if the next slot is skipped, it's correct...
I'm experiencing the same issue and I confirm that the workaround of setting prevMillis to Date.now() doesn't work effectively, it works 2-3 times but then the job schedulation is not...