v2.4.10: Scheduled Tasks Fire at the Time You Picked, and Survive a Cleared Conversation

A scheduled task has exactly one job: fire at the right moment, every time. When it does not, you usually find out the hard way, by noticing something that should have happened did not. v2.4.10 is a small, focused release that fixes two scheduling bugs doing precisely that kind of quiet damage.

Here is what changed.

Scheduled tasks now run at the time you actually chose

This one was subtle and genuinely frustrating. When you scheduled a task from the interface, the time you picked was being shifted by your timezone offset before it was stored. Set something for 9:10 and it was saved as 6:10. The task then fired hours early, and if that shifted moment had already passed for the day, it never fired at all.

The scheduler now stores and interprets the time in your local timezone, exactly as you entered it. What you pick is what runs. No mental math, no offset, no tasks silently landing in the past.

One housekeeping note: any task you created before this release still carries the old, shifted time. Recreate those so they pick up the corrected schedule. It takes a moment and saves you from a reminder that fires three hours off.

Scheduled tasks keep working after you clear a conversation

The second bug was harder to spot because nothing looked broken. After you cleared a conversation, a scheduled task tied to it could quietly stop triggering. The task still fired on time internally, but the message never reached the agent, so nothing actually happened on the other end. No error, no clue, just silence where a daily digest or a recurring check used to be.

Clearing a conversation no longer breaks scheduling. The scheduled prompt is delivered reliably now, whether or not the conversation was recently cleared, so your recurring work survives a tidy-up.

Why a two-fix release still matters

It is tempting to bundle small fixes and wait for a headline feature to ship them alongside. We would rather not sit on these. Scheduling is one of those features you stop thinking about precisely because it works, and both of these bugs broke that trust in the quietest possible way: a reminder that fired at the wrong hour, a digest that just stopped arriving. When an AI employee is running your recurring tasks unattended, "fires at the exact time you picked, every time, no matter what else you did" is not a nice-to-have. It is the whole point.

If you have scheduled tasks set up, this is worth a two-minute pass: recreate anything created before today so it inherits the corrected timezone handling, and rest easy that clearing a conversation will not quietly cut a task loose.

Want to test the most advanced AI employees? Try it here: https://Geta.Team