Recover from setup errors

Interpret errors before retrying an authorized operation.

Before you start

  • Use the correct company and an active account with permission for this workflow.

Where to go

Workspace → Recover from setup errors

Audience

Authorized users of the selected workspace.

Permissions

  • Use your current account role; a Help link does not grant permission.

Workflow

  1. Check your company, account state, connectivity and session. Preserve non-secret input before signing in again.
  2. For 401 sign in again or check the server credential. For 403 ask the owner to review role, account binding and assigned scope.
  3. For 404 verify the supported route. For 409 reload the current state before deciding whether another action is necessary. For 422 correct the indicated fields.
  4. For 429 wait as directed before explicitly retrying. For offline or 5xx, check connectivity and retry a read; verify state before repeating a mutation.
  5. Configuration unavailable and not released are distinct from session errors. Follow the availability explanation and provide support only sanitized status and timing.

Expected outcome

Read the current saved state in the workspace after the permitted action; Help does not perform or verify the action.

Troubleshooting

A retry could duplicate an action
Inspect the current saved result first. Never include keys, tokens, personal records or callback payloads in a support report.