The main timeout users normally choose is the maximum Devin worker duration:
The default is 12 hours. Set a shorter value when cost containment matters more than
allowing long-running Devin sessions to remain connected.
Why the Modal timeout is longer
Stopping the worker begins the final phase of the session lifecycle. The Sandbox may still
need time to start, confirm the final Devin state, preserve a filesystem, and clean up.
The generated application therefore uses a derived function timeout:
Keep this property in the decorator. It automatically stays aligned when session or
recovery timing changes.
Tune safely
- Set
session_timeout_seconds for the longest worker run you want to allow, then
keep the generated function timeout property unchanged.
- Change readiness or snapshot timing only when logs identify that specific phase
as the bottleneck.
- Change API retry timing only for a known network or upstream reliability need.
Omit timeout= from run_session(). An independent Sandbox timeout can interrupt
recovery or cleanup.
