Track cancel and retry managed AI requests safely

Before you start

Keep the request ID and idempotency key from the original submission. Use the same customer account for subsequent operations.

Steps

1. Inspect the request status using the playground or ispeed-ctl requests show.
2. Use wait or status polling while queued or running; waiting does not resubmit the job.
3. Cancel only a queued request using a supported cancellation control. A running request cannot be canceled through this path.
4. For a failed or expired request, verify reservation release in the request and wallet history.
5. Retry an uncertain identical submission with its original idempotency key. Use a new key for a deliberately new workload, not for every polling attempt.

Example

ispeed-ctl requests show REQUEST_ID
ispeed-ctl requests cancel REQUEST_ID
ispeed-ctl requests wait REQUEST_ID --timeout 10m

Check the result

One submission produces one request, and settlement or refund follows its terminal state.

Troubleshooting

A canceled or failed request can still have audit history. Reusing a key with changed input is rejected. If a request stays stuck, send support its ID and timestamps rather than repeatedly purchasing replacements.