Good question! There's no such thing as a "running" task/job at the moment (i.e., a start signal). The closest thing is lengthening the grace period, but that also means that the notification is delayed, so it's not really a solution. This is in the backlog.
The usual fix is a second ping at the start of the job: the schedule check watches the start ping, and a separate “max runtime” check watches the gap between start and finish. You get alerted promptly either way without inflating the grace period.
adityamishra241 · · focus · HN ↗
4815162342 · · focus · HN ↗
msupuka · · focus · HN ↗