Usage logs and request diagnosis
Locate a request using its timestamp, model, and error details.
Find the request
Open usage logs for your site. Select the request time range and use the model, key, or account filters actually available. Check the displayed timezone and your access scope; organization members only see permitted records.
Compare the timestamp, complete model ID, HTTP status, error code, and request ID if provided. Records may take time to appear. An empty list alone does not prove that a request never reached the service or incurred no charge.
Check usage and charges
Distinguish input, output, and cache measurements shown by the page. Request count is not token count. Use the same account, model, and time range when comparing balance and billing.
Prepare a support report
Keep a redacted error response, timestamp and timezone, model ID, client name and version, and whether streaming or tools were enabled. Never include Authorization headers, keys, full private conversations, or personal data.
Follow Troubleshooting first. Public documentation feedback is for article issues, not private business logs.