From d46f2c3381bcda603ad77cbff458d2150a74794f Mon Sep 17 00:00:00 2001
From: "promptless[bot]" <179508745+promptless[bot]@users.noreply.github.com>
Date: Mon, 23 Mar 2026 17:39:43 +0000
Subject: [PATCH] Document runsync client timeout behavior

---
 flash/apps/requests.mdx            | 2 ++
 flash/configuration/parameters.mdx | 4 ++++
 2 files changed, 6 insertions(+)

diff --git a/flash/apps/requests.mdx b/flash/apps/requests.mdx
index 44edb6fa..5c3205b1 100644
--- a/flash/apps/requests.mdx
+++ b/flash/apps/requests.mdx
@@ -85,6 +85,8 @@ curl -X POST https://api.runpod.ai/v2/abc123xyz/runsync \
 }
 ```
 
+The `/runsync` endpoint has a 60-second client-side timeout by default. If you've configured `execution_timeout_ms` on your endpoint, the client timeout uses that value instead. For jobs that take longer than 60 seconds, set `execution_timeout_ms` to prevent `/runsync` requests from timing out.
+
 <Tip>
 Use `/run` for long-running jobs that you'll check later. Use `/runsync` for quick jobs where you want immediate results (with timeout protection).
 </Tip>
diff --git a/flash/configuration/parameters.mdx b/flash/configuration/parameters.mdx
index a79c75f7..d8e14872 100644
--- a/flash/configuration/parameters.mdx
+++ b/flash/configuration/parameters.mdx
@@ -346,6 +346,10 @@ async def train(data): ...
 async def infer(data): ...
 ```
 
+<Note>
+The Flash SDK's `runsync()` method uses your `execution_timeout_ms` value as the client-side HTTP timeout. If set to a positive value, the SDK waits that duration for the job to complete. If unset or set to `0`, the SDK defaults to a 60-second timeout. For long-running inference jobs, set `execution_timeout_ms` to prevent premature timeouts.
+</Note>
+
 ### flashboot
 
 **Type**: `bool`