@DanielMorales9 This is an interesting idea, but it needs more discussion.

I think we can remove the need for the global variables, while also making the behavior more stable by making a change to your logic.

The main goal I want to achieve is that even if we are not "at a scheduled update time" we should revert to the slot_count that would have been most recently applied (if someone makes a manual change in the UI we should revert it at the next sync, for example).

We can do this by using the croniter.get_prev() function on each of the defined schedules at each sync using the current time as the start_time, and applying the schedule with the most recent previous time.

For example:

croniter(expr_format="0 12 * * *", start_time=datetime.now()).get_prev(ret_type=datetime)

This approach means we have no state to hold, and there is no ambiguity at the first sync about which schedule to use. Also note, in this approach the non-schedule slots defined in the user's values will never be applied.

@DanielMorales9 thanks for your patience, I will be including this in the 8.7.0 chart release today!

Also, I have pushed a commit to your branch with some changes and docs in preparation for this.