Deploy Rate Limit Exceeded

deploy-rate-limit-exceeded · 429

The workspace has started as many deployments in the rolling window as the limit allows, so the API didn't start this one.

The limit is 30 starts in 60 minutes by default, counted across the workspace although detail says per user. retryAt is when the oldest counted start ages out and frees a place, and retryAfterSeconds the wait until then. A rollback isn't counted.

Besides the members every error carries, this type adds limit, windowMinutes, retryAfterSeconds and retryAt.

Common causes

  • A script or an agent deployed in a loop, such as on every saved change.
  • Several members or keys deployed in the same workspace within the window.

How to fix the call

  • Wait until retryAt, then deploy once.
  • Gather changes into fewer deployments rather than one per change.
  • To go back to an earlier version meanwhile, roll back: ghaym cloud deployments rollback <id> isn't counted.

Example response

json
{
  "type": "deploy-rate-limit-exceeded",
  "title": "Deploy Rate Limit Exceeded",
  "detail": "This account has started 30 deployments in the last 60 minutes, which is the per-user limit. Try again after 2026-07-28T09:49:05.000Z (about 1145 seconds).",
  "limit": 30,
  "windowMinutes": 60,
  "retryAfterSeconds": 1145,
  "retryAt": "2026-07-28T09:49:05.000Z",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
  "status": 429,
  "docs": "https://ghaym.me/docs/errors/deploy-rate-limit-exceeded"
}