Description
On both the Auto-schedule page and the Mission Control page, auto-scheduled missions are sometimes visualized as Skipped even though they are correctly scheduled on the backend. Refreshing the page makes them appear correctly as Scheduled.
Steps to reproduce
- Open the Auto-schedule page (or the Mission Control page).
- Observe today's auto-scheduled time slots.
- Sometimes one or more slots are rendered as "Skipped" even though they have not been skipped.
- Refresh the page — the same slots now correctly show as "Scheduled".
Note: this is not consistent and does not always happen. It appears intermittently, which makes it harder to reproduce on demand.
Expected behavior
A mission slot should only be rendered as "Skipped" when the user has actually skipped it. The visualization should remain consistent with the backend state without needing a manual refresh.
Suggested direction (for whoever picks this up)
- Consider introducing a distinct "Pending" / "NotYetScheduled" visualization state so that transient or loading conditions are not presented to the user as "Skipped".
- Investigate how auto-schedule data is loaded and updated on the frontend (initial fetch vs. live updates) to see whether a race or stale snapshot could be causing the visualization to fall back to "Skipped".
Description
On both the Auto-schedule page and the Mission Control page, auto-scheduled missions are sometimes visualized as Skipped even though they are correctly scheduled on the backend. Refreshing the page makes them appear correctly as Scheduled.
Steps to reproduce
Note: this is not consistent and does not always happen. It appears intermittently, which makes it harder to reproduce on demand.
Expected behavior
A mission slot should only be rendered as "Skipped" when the user has actually skipped it. The visualization should remain consistent with the backend state without needing a manual refresh.
Suggested direction (for whoever picks this up)