Octokit::ServiceUnavailable: POST https://api.github.com/repos/exercism/backup/dispatches: 503 - No server is currently available to service your request. Sorry about that. Please try resubmitting your request and contact us if the problem persists. (Octokit::ServiceUnavailable)

## Error

```
POST https://api.github.com/repos/exercism/backup/dispatches: 503 - No server is currently available to service your request. Sorry about that. Please try resubmitting your request and contact us if the problem persists. (Octokit::ServiceUnavailable)
```

## Stack trace

```
octokit/response/raise_error.rb:14 in on_complete
faraday/middleware.rb:19 in block in Faraday::Middleware#call
faraday/response.rb:61 in on_complete
faraday/middleware.rb:18 in call
octokit/middleware/follow_redirects.rb:73 in perform_with_redirection
octokit/middleware/follow_redirects.rb:61 in call
faraday/retry/middleware.rb:140 in call
faraday/rack_builder.rb:154 in build_response
faraday/connection.rb:516 in run_request
faraday/connection.rb:283 in post
```

## Tracking Details
- **Project**: exercism-rails
- **Sentry**: [Octokit::ServiceUnavailable: POST https://api.github.com/repos/exercism/backup/dispatches: 503 - No server is currently available to service your request. Sorry about that. Please try resubmitting your request and contact us if the problem persists. (Octokit::ServiceUnavailable)](https://thalamus-ai.sentry.io/issues/141201877/)
- **Culprit**: MandateJob
- **First seen:** Aug 17, 2026

Start by locating MandateJob in the exercism-rails codebase and tracing its Octokit POST to the GitHub dispatches endpoint, using the supplied stack trace and Sentry report. Determine whether the 503 is transient or requires changed handling; the issue is complete only once the expected behavior for this failure is defined and verified.

Written by the indexing model from the issue text.