Request IDs and Correlation
How request IDs connect client errors, logs, and support evidence.
Carry the response x-request-id into a sanitized support record.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The API accepts a safe incoming x-request-id or creates a UUID, returns it on the response, and includes it in the error envelope as requestId. Authorization and cookie headers are redacted from structured logs.
| Check | Source-backed expectation |
|---|---|
| Scope | A request ID identifies a diagnostic slice; it is not an authorization credential. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i -H 'x-request-id: phase6-demo-1234' https://api.example.invalid/health |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
curl -i -H 'x-request-id: phase6-demo-1234' https://api.example.invalid/health
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.