Drop legacy runtime routes - #175
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c569cf23a2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| case "${suffix}" in | ||
| scheduler) | ||
| schedule_time="${main_time}" | ||
| scheduler_path="/run" |
There was a problem hiding this comment.
Update heartbeat matching before switching jobs to /run
When the scheduler sync rewrites the main job to ${service_url}/run, the scheduler-aware heartbeat no longer recognizes that job: scripts/execution_report_heartbeat.py only treats scheduler URIs with path / as strategy-run jobs and then includes a service when no matching job is found. For less-frequent targets such as monthly services, this makes every configured service look due on every heartbeat run, causing false missing-report alerts/failures even on days the main scheduler did not run. Update the heartbeat matcher to accept the new /run path as part of this route migration.
Useful? React with 👍 / 👎.
Summary
Tests