Schedule "StartAt" not used when calculating intervals?

Today is June 19th, 2024. If you create a schedule and specify "every 365 days" the result will be that the first run is on 2024-12-18 00:00:00. That's in 6 months. I've tried passing StartAt: 2025-06-19 but I get 2025-12-18 00:00:00 as a result.

I understand this may be known and as-designed behavior but it struck me as unexpected to ask for a 365 day interval, yet the first run is within the next 6 months.

I also don't see any way to achieve my desired result. Am I missing anything?

EDIT: I also can't use the offset to control this behavior because I don't know what the final calculation will be until the schedule is created.

Expected Behavior

In the example above, I'd prefer to have the schedule's first run be at my specified "StartAt". So, if I say:

"Start this workflow every 365 days with start at 2025-02-03 04:05:06", then the upcoming runs would look like:

• 2025-02-03 04:05:06
• 2026-02-03 04:05:06
• 2027-02-03 04:05:06
• etc.

Actual Behavior

When I pick 365 days as the interval, I seem to be getting a date 6 months in the future.

Steps to Reproduce the Problem

1. Go to temporal UI and add a schedule.
2. Choose 365 days and save.
3. Check the schedule's upcoming runs.

Specifications

• Version:
• Platform: