TL;DR: Set max_duration generously above your longest expected job or the session gets killed mid-run; set idle_timeout so forgotten sessions get reaped instead of running to the default. [Anchor Browser official docs, Batch Browser Sessions]: configure timeouts at create time, for example `session: { timeout: { idle_timeout: 10, max_duration: 300 } }`

## Fix
1. Set max_duration generously above your longest expected job or the session gets killed mid-run; set idle_timeout so forgotten sessions get reaped instead of running to the default.
   Expected: this specific failure stops.

## Details
[Anchor Browser official docs, Batch Browser Sessions]: configure timeouts at create time, for example `session: { timeout: { idle_timeout: 10, max_duration: 300 } }` . The shape is the same for sync, async, and batch creates. Sessions accept `session.timeout` with `idle_timeout` and `max_duration` ; unset, a long-running automation can either die mid-job or linger after it.

## When to use
You hit exactly this: Anchor Browser: set idle_timeout and max_duration at create, or long jobs get killed in Anchor Browser.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Anchor Browser.

## Edge cases
- Source context: Official docs (Batch Browser Sessions): documents the session timeout gotcha that trips agents running long Anchor Browser jobs.