Maintenance and Busy
Pushes are suspended for maintenance; clone and fetch still work - Git access is suspended for maintenance - The repository is busy with another write - The git service is busy.
Maintenance and Busy Messages
Symptom
A push during maintenance (HTTP 503):
remote: Pushes are suspended for maintenance; clone and fetch still work
Other messages from the same family, on any git operation:
Git access is suspended for maintenance, please try again later
The repository is busy with another write, please try again in a moment
The repository is locked for maintenance, please try again later
The git service is busy, please try again in a moment
Over HTTPS they come after remote:; over SSH they appear alone.
Cause
| Message | Cause |
|---|---|
Pushes are suspended for maintenance | The instance is in maintenance: pushes wait, clone and fetch still work |
Git access is suspended for maintenance | Full maintenance: every git operation waits |
The repository is busy with another write | Another push or a web action is writing to the same repository right now |
The repository is locked for maintenance | A short maintenance task runs on this repository |
The git service is busy | The server has too many git operations at this moment |
Diagnose
Read the message: each one names its cause. None of them means a problem in your clone.
Fix
Option A - Retry (recommended)
Wait a moment for the busy messages, longer for the maintenance ones, then run the same command again. Your local commits are safe.
Option B - Keep working locally
During a push freeze, keep committing locally and push once maintenance ends. Clone and fetch still work.
Verify
git push
The push ends with the branch update line, with no maintenance or busy message.
Prevent
- In CI, retry a git step a few times with a delay when it fails with one of these messages.