Errors and recovery

Read the error code, message and next action together. A missing response is not proof that an operation failed.

Session and permissions

Sign in again after session expiry. The console clears private caches and one-time results before showing another owner. Unknown and wrong-organisation resources share a safe unavailable response. Do not retry with a broader credential automatically.

Lost creation response

Keep the original idempotency key, trimmed repository name and request ID. Retry or resume that same request. Card verification, allocation and readiness are separate; a browser callback is not creation confirmation.

Lost credential response

A secret is returned once and cannot be replayed. Resolve the original key's public metadata before revocation and reissue. If several keys could match, ask an operator to reconcile them rather than guessing.

Merge or replacement uncertainty

Refresh the same public operation. Do not assume a timeout means the upstream rejected a change. A replaced generation requires fresh references, not a forced retry against old state.

Meter and payment failures

An unavailable meter is not zero. A provider outage does not create a customer payment deadline. Saving a card is not invoice payment. Keep cleanup accessible while payment is restricted.