## TL;DR

Escalate the timeout before giving up: first retry at the default 30s, then pass --render-options with timeout 60000, then a third attempt with render_type idle0 and timeout 90000 to wait for full network idle. Each step is one flag, and the page that timed out at 30s often extracts cleanly at 90s. A timed-out Nimble extract with --render does not mean the page is unscrapeable - JS-heavy pages just take longer to settle.

## Fix

1. Escalate the timeout before giving up: first retry at the default 30s, then pass --render-options with timeout 60000, then a third attempt with render_type idle0 and timeout 90000 to wait for full network idle.
   Expected: You get the expected result; the problem is gone.
2. Each step is one flag, and the page that timed out at 30s often extracts cleanly at 90s.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are dealing with this situation.
- The symptom matches: Nimble rendered extract timing out - escalate 30s to 60s to 90s with render_type idle0 before quitting.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source. Source: https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md.

## Variant phrasings

### Nimble rendered extract timing out - escalate 30s to 60s to 90s with render_type idle0 before quitting

## Why it happens

Nimble's own error-handling reference (render timeout escalation): never give up after a single timeout on a rendered extract. Retry with increasing timeouts: attempt 1 default 30s, attempt 2 with --render-options '{"timeout": 60000}', attempt 3 with --render-options '{"render_type": "idle0", "timeout": 90000}' waiting for full network idle. Only after all three time out should you escalate to heavier investigation.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md