How to prevent a cron-scheduled workflow run from timing out at the execution timeout?

Suppose you schedule a cron every minute for a day (using execution timeout of 1 day).
Should the last run be allowed to finish even if it goes over? Otherwise you could end the schedule with a half-finished workflow.
I think this failure would be more common if the interval period didn’t evenly divide into the execution period.
Any best-practices I’m missing here?

One option is to check the time at the beginning of the workflow and skip the run if not enough time left.

Thanks. It feels like a rough edge in the framework; I wonder if there’s a real use case for the execution timeout to just cut off a run in a recurring workflow. Maybe there should be another timeout that dictates when runs can start?

Yes, having such timeout sounds very reasonable. Would you file an issue to get this idea tracked?