Public Endpoint wan-2-2-i2v-720 — generation errors, no logs, status “request does not exist”
I’m using the RunPod Public Endpoint:
- Model: wan-2-2-i2v-720
- API base: https://api.runpod.ai/v2/wan-2-2-i2v-720/
On 15 Dec 2025 23:43 to 16 Dec 2025 04:15 UTC — multiple generation requests started failing for unknown reasons.
Unfortunately I didn’t save the full error bodies at the time, and now checking status returns:
{ "error": "request does not exist" }
I understand job results expire after a short time (e.g. /run ~30 minutes, /runsync ~1 minute unless using ?wait), so I can’t retrieve those old requests anymore. :contentReference[oaicite:1]{index=1}
Is there any way (for me or RunPod support) to determine the root cause of the generation failures I experienced on the Public Endpoint
Any pointers appreciated — I just want to understand what caused the errors.
- Model: wan-2-2-i2v-720
- API base: https://api.runpod.ai/v2/wan-2-2-i2v-720/
On 15 Dec 2025 23:43 to 16 Dec 2025 04:15 UTC — multiple generation requests started failing for unknown reasons.
Unfortunately I didn’t save the full error bodies at the time, and now checking status returns:
{ "error": "request does not exist" }
I understand job results expire after a short time (e.g. /run ~30 minutes, /runsync ~1 minute unless using ?wait), so I can’t retrieve those old requests anymore. :contentReference[oaicite:1]{index=1}
Is there any way (for me or RunPod support) to determine the root cause of the generation failures I experienced on the Public Endpoint
wan-2-2-i2v-720/status/run/runsyncAny pointers appreciated — I just want to understand what caused the errors.
