The scheduled monitoring workflows (health-check.yml, ripe-atlas-check.yml) had their schedule: triggers removed before going public, because on a public repo the run logs would expose live endpoints / measurement targets, and public cron auto-disables after 60 days of inactivity anyway. They are currently manual-dispatch only.
Track the proper long-term home for monitoring:
Until then, run them by hand with workflow_dispatch.
The scheduled monitoring workflows (
health-check.yml,ripe-atlas-check.yml) had theirschedule:triggers removed before going public, because on a public repo the run logs would expose live endpoints / measurement targets, and public cron auto-disables after 60 days of inactivity anyway. They are currently manual-dispatch only.Track the proper long-term home for monitoring:
.targetvalues from any logged outputUntil then, run them by hand with
workflow_dispatch.