Sections
Docs version v1 Current version
Agent-readyHuman guide
Support escalation
Escalate issues with the request_id, the error code, and the right severity.
View as MarkdownEvery failed request carries a request_id in its error envelope. It lets support trace the exact request without you sharing any secret.
Before you escalate
- Capture
error.codeandrequest_idfrom the failing response. - Look the code up in the error codes catalog.
- Retry once with backoff only if the code is marked retryable.
- Note the deployment or job ID if the failure came from a deploy.
Open a support request
$yalla support ticket --request-id <request-id> The same flow is available from the control plane: every error surface shows a copyable request_id next to its support link.
What support can see
Support sees request metadata, audit events, and job state — never secret variable values, tokens, or payment credentials. Those stay redacted end to end.
Caution: If you suspect a secret was exposed, rotate it first with yalla variables set <KEY>, then escalate with the request_id — see security boundaries.