Design every RunPod-proxied endpoint to answer fast and poll for results: return a job id from the first call and check status separately. Reserve the HTTP proxy for short UI requests; use direct TCP for WebSockets, long polls, and big payloads. If jobs die at exactly 100 seconds, it is the proxy cap, not your code.

Context: RunPod's official gotchas reference documents the proxy 524 trap. Requests through the RunPod HTTP proxy die at about 100 seconds with a 524 because the proxy runs through Cloudflare, which caps connection time at 100 seconds. The fix is to never hold a single request open that long: return a job id and poll, use background queues or progress endpoints, or use direct TCP instead of the proxy for long-lived connections.

## Matched source
Source: Published skill
Original query: "RunPod proxy kills requests at 100 seconds, poll with a job id instead"
Key terms: instead, kills, poll, proxy, requests, runpod, seconds