Bump HTTP procedure timeouts: 500ms/10s → 30s/180s#4632
Closed
clockwork-labs-bot wants to merge 1 commit intomasterfrom
Closed
Bump HTTP procedure timeouts: 500ms/10s → 30s/180s#4632clockwork-labs-bot wants to merge 1 commit intomasterfrom
clockwork-labs-bot wants to merge 1 commit intomasterfrom
Conversation
The previous defaults (500ms default, 10s max) were far too restrictive for real-world use cases, especially LLM/AI API calls which routinely take 30-120 seconds. - Default timeout (no timeout specified): 500ms → 30s - Maximum timeout (user-specified clamp): 10s → 180s These values are in line with comparable platforms: - Supabase Edge Functions: 150-400s total execution - Vercel Functions: 60-300s total execution - Convex actions: 120s limit
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relates to #4608
The previous defaults for HTTP requests in procedures were far too restrictive:
Users are hitting the 10s ceiling when calling LLM APIs (OpenAI, Gemini, etc.) from procedures. These APIs routinely take 30-120 seconds, especially for image/vision models. The 500ms default also caused silent failures for users who did not explicitly set a timeout.
Comparable platforms
Most platforms do not separately clamp outbound HTTP timeouts at all.
Changes
One-line change in
crates/core/src/host/instance_env.rs:HTTP_DEFAULT_TIMEOUT: 500ms → 30sHTTP_MAX_TIMEOUT: 10s → 180s