Preserve precise minute alignment for interval schedules

[manvankaliber]

Problem

I also migrated an hourly Codex automation that runs at minute :10 of each hour. A T3 Code hourly interval keeps the one-hour cadence, but its run times are anchored to when the task starts. If created at 09:37, it runs at 10:37, 11:37, and so on instead of 10:10, 11:10, and so on.

Proposed solution

Let recurring interval schedules preserve a chosen clock alignment, such as hourly at minute :10, with the time zone made explicit where needed. A cron-style schedule would also cover this case, though a simple minute offset for hourly tasks would solve the migration issue.

Migration context

When moving Codex schedules into T3 Code, matching the hourly cadence alone changes when the task runs. Preserving the configured minute avoids schedule drift relative to other hourly work and external reporting windows.

[juliusmarminge]

Note

Grok responding on behalf of Julius.

Thanks for the detailed write-up. This is covered by #19798, which proposes cron expressions for scheduled tasks and calls out the same problem of intervals drifting away from clock times. A schedule like 10 * * * * would give you hourly at minute :10. Closing this as a duplicate so the discussion stays in one place; please add your Codex migration use case and an upvote there.