HELP / GETTING STARTED

Investigate a request and replay it

Find an outcome, understand its charge and reopen its inputs deliberately.

Narrow the history

Activity shows request metadata for your account. Use the time range, operation, status and text filters to find the work you need. Open a request to inspect its ID, operation, target or query, result state, elapsed time and credit charge.

Use the final request state when reconciling cost. A running reservation and a completed charge are different states. If the source failed, read the recorded error before deciding whether another attempt is useful.

Replay as a new request

Reopen the request in the workbench to review its inputs and generated code. Loading the replay does not execute it. Check the parameters, especially for older requests whose full original inputs may not have been retained, before choosing Run.

Replay asks the source for fresh information. It does not recover the old response, and a successful run is charged normally. For a lost response after a timeout, reconcile the original request first.

Export the right data

Activity CSV exports the matching request metadata, up to 5,000 rows. Narrow the date range or other filters if you need a smaller export. Request metadata is retained for 30 days.

Activity shows synchronous request metadata rather than full response bodies. Optional Idempotency-Key protection can replay a retained response for up to 24 hours. Download the result while it is available in your request screen, or use Collections when you need page content saved for later retrieval. Collection downloads have their own seven-day expiry.

YOUR PRIVACY

Choose what works for you. You can reopen these settings from the footer at any time.