RunMyJob GitHub Runners restricted by GitHub API
Started at
•Resolved
Component: Cache Action Status: Operational
We’ve successfully republished the puzl-cloud-cache
action to GitHub Marketplace. You can use it normally under the same name https://github.com/marketplace/actions/puzl-cloud-cache
Thank you for your patience! RunMyJob GitHub runners are functioning as expected.
Identified
Status: Partial Service Restored
GitHub Runners: Operational
Cache Action: Degraded
What’s Changed
- All queued workflows are now being picked up and completed successfully.
- Jobs are running normally on our GitHub App.
Current Issue: Cache Action Unavailable
Attempts to re-publish our action to GitHub Marketplace are returning 500 Internal Server Errors.
This prevents the updated versions from going live.
Mitigation In Progress
- Collaborating with GitHub Support to resolve any upstream issues.
Next Update
We’ll post another update by 19:00 UTC today or sooner if critical developments occur.
We apologize for the inconvenience and appreciate your patience as we restore full cache functionality.
Identified
GitHub Runners Impacted
Impact
- RunMyJob GitHub runners failed to pick up or complete user workflows.
- Jobs remain queued or time out.
What Happened
At approximately 04:00 UTC, our monitoring detected repeated 403 “rate limit exceeded” errors from the GitHub API. This prevented runners from authenticating API requests and servicing jobs. After a short period of time, puzl-cloud
GitHub application has been silently restricted by GitHub.
Mitigation In Progress
- Spinning up a reserved GitHub App to avoid restrictions.
- Updating our orchestration layer to authenticate every request through the new App.
Next update: 2025-07-10 14:00 UTC (or sooner if critical developments occur)
We apologize for the disruption and are working to restore full CI/CD capacity.