Request history

One row per authenticated render in the last seven days, newest first, synchronous calls and jobs alike: kind, outcome, safe error code, cache hit or miss, the meter it counted against and the quantity it committed (0 for a cache hit or a failure), response size and type, duration, the target's origin and path, the names of the option fields supplied, the request id you can quote to support and, for a render that loaded a page, its diagnostics (Diagnostics). A cache hit rendered nothing and has none. A job cancelled before it ran, or failed because no worker could finish it, has its row too.

It is diagnostic, not replay. Nothing here can rebuild the request: header and cookie values, HTML, template variables, URL query strings and signatures are never recorded. Retention is seven days for every account.

id matches the request id, a job id or your own X-Request-ID, which is how you arrive here from an error message.