Posted match times don’t reflect updated schedule after “Send to FIRST”

[dandominicstaicu]

Describe the bug
When the scorekeeper adjusts the event schedule during the day (e.g., moving a break earlier), the schedule displayed in the ftc-scoring website account does not update after the event is “Sent to FIRST.” The posted match times appear to remain based on the original schedule, which causes incorrect cycle time values and an incorrect average cycle time calculation.

To Reproduce
Steps to reproduce the behavior:

1. Create/load an event with an initial schedule in FTC Scoring (desktop).
2. During the event, adjust the schedule (e.g., move a break earlier / modify start times).
3. Verify on venue tablets / FTC-Live that the updated schedule is reflected correctly (Event Report shows correct times/breaks).
4. Use “Send to FIRST” from FTC Scoring.
5. Log into the ftc-scoring website account and open the event.
6. Observe that posted match times still resemble the original schedule (some matches show ~70 min cycle time; others show ~8 min and “(B)”), leading to an incorrect average cycle time.

Expected behavior
After the scorekeeper changes the schedule and sends the event to FIRST, the ftc-scoring website should reflect the updated schedule (match times and breaks), and cycle time / average cycle time should be calculated from the updated posted times.

Screenshots
If applicable, add screenshots to help explain your problem.

Screenshot from my Head Referee account on Cycle Time Report on event ROSLT

I do not have screenshot from tablet during the event.

As you can see from this screenshot, the 1st break was moved from after Q11 to after Q5 (change was made on local and could be seen on the tablets).
Also break from after Q22 was moved to after Q16.

Device (please complete the following information):

• OS: MacOS/Windows
• Browser chrome/safari
• Version any

Additional context

• The schedule/times/breaks were correct on the event tablets connected to FTC-Live at the venue (Event Report looked correct).
• The problem only appears on the posted times visible when viewing the event through my ftc-scoring website account.
• This results in inconsistent per-match cycle times (e.g., ~70 minutes for some matches, ~8 minutes for others with a “(B)” marker) and an incorrect average cycle time.
• Question: Is there a required workflow for mid-day schedule edits (e.g., re-publish/regenerate something before “Send to FIRST”), or is the website failing to ingest updated schedule changes?