docs: Document valid range for idle_timeout parameter

[promptless]

Open this suggestion in Promptless to view citations and reasoning process

Adds the valid range (1-3600 seconds) to the idle_timeout parameter documentation in Flash. This helps users configure the parameter correctly upfront, avoiding validation errors at construction time.

Trigger Events

runpod/flash PR #287: fix: AE-2316: idletimeout must be in valid range

Promptless Research (5 files, 1 GitHub PR)

• Reviewed runpod/flash#287
• Viewed .long_term_context/product_knowledge/product_overview.md
• Viewed .long_term_context/doc_workflow/client_instructions.md
• Viewed flash/configuration/parameters.mdx
• Viewed flash/execution-model.mdx
• Viewed .long_term_context/style/client_style_guide.md

Agent Response

I've reviewed PR #287 and created a documentation update.

Summary

The PR adds field validation for idleTimeout to ensure values are between 1 and 3600 seconds. This validation was already enforced by the backend but now happens at construction time, giving users earlier feedback.

Documentation change

I added the valid range to the idle_timeout parameter documentation in flash/configuration/parameters.mdx:

**Type**: `int`
**Default**: `60`
**Valid range**: 1-3600 seconds

This helps users configure the parameter correctly upfront. While the recommendations in the docs (30-300 seconds) fall well within this range, the upper limit of 1 hour is a backend-specific constraint that users wouldn't know without documentation.

Suggestion created: Document valid range for idle_timeout parameter

---

Tip: Planning a big docs refactor? Use Deep Analysis to get help with the heavy lifting 🔍

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
runpod-docs	🟢 Ready	View Preview	Mar 25, 2026, 9:21 PM

[promptless]

Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.)