Provider HTTP 429 rate limiting: pin failing cron jobs to alternate provider
brain-distill · confidence medium · status active
tags: infra cron reliability
When openai-codex returns HTTP 429 usage_limit_reached for cron jobs (engagement-os-daily-opportunity-scout, engagement-os-evening-progress-review, pro-control-room-status-brief), pin those specific job IDs from ollama-launch/kimi-k2.7-code:cloud to openai-codex/gpt-5.6-sol (or another available provider) and trigger each with hermes cron run. Do not restart gateways or change config, provider quota is upstream, not a local service issue. After pinned reruns succeed, run cron_readiness_audit to confirm GO status.
Sources:
/Users/dwayne/clawd/memory/health-remediation.log