Hey all, thanks for sticking with this thread and for the detailed timings, they helped a lot.
Two updates. First, we rolled out a change yesterday evening (UTC) to how scheduled routines are queued at busy times. Before, a routine that hit the queue during the US morning could retry for a while and then be skipped for the day with nothing shown in the app. Now each routine gets a reserved slot a few minutes out and runs in it, so skipped runs should stop. Runs can still start a few minutes after the scheduled time during the busiest hours, but the long delays and the silent skips should be gone. We are watching it over the next few days.
Second, if you edited a routine’s schedule or switched it off between Sep 4 and Sep 8 and it kept running on the old settings, that was a separate server-side problem that has been fixed. Please re-save any routine that still looks wrong.
@nithish654, your every-10-minute window (9:00 to 3:50 PM New York) sits exactly in the hours that were affected, so what you saw matches this. If a run still starts more than about 15 minutes late after today, reply with the routine name, the scheduled time, and the time it actually started, and I will take a look.
On the “did it run?” confusion: a scheduled run happens in the background and only posts to the chat if it decides it has something to say. If you always want a message, tell the routine in plain words to send you a message with the result (even a one-line “nothing to report” is fine). That makes the run post every time.
@Andrew_Simard, the external ping workaround should no longer be needed, but it does no harm to leave it for a day or two while you confirm.