CRON / scheduled trigger

Scheduled workflows have a failure mode webhook-triggered ones don't: nobody notices when they silently stop firing. A workflow triggered by a real event fails loudly when the event doesn't produce the expected result, but a CRON job that stops running just produces silence, no report shows up, no digest gets sent, and often nobody checks until a client asks where last week's report went. Scheduled workflows need their own separate monitoring, a check that confirms the job actually ran, not just that it works when tested manually.