Found what looks like a bug. The scheduled event start timestamp is at 3:24 PM but the flow itself is scheduled for 4 AM and ran at that time.

We should fix it bc it’s unintuitive, but tldr if I scheduled a run for my birthday next year, the UI would say it was scheduled today. That datetime reflects when the schedule was created, not when the flow run is supposed to begin. It’s some weird pedantry that’s confusing IMO but that’s the disparity

Thanks for the explanation. I tend to agree that the information of when this specific flow run was initially scheduled is not exactly useful. Being able to know when schedules were changed for a deployment is useful for auditing and debugging but this is not the optimal place to do that IMO.

Yep, totally agree.