## TL;DR

Reserve the HTTP proxy for short UI requests; use direct TCP for WebSockets, long polls, and big payloads. 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.

## Steps

1. 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.

## When to use

You are seeing this: Design every RunPod-proxied endpoint to answer fast and poll for results: return a job id from the first call and check status separately. Use this skill when you run into "RunPod proxy kills requests at 100 seconds, poll with a job id instead".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.