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

A timed-out Nimble extract with --render does not mean the page is unscrapeable - JS-heavy pages just take longer to settle. 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. Agents that abort after the first timeout leave easy wins on the table.

Context: 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.

Matched source

Source: Source: https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md Original query: "Nimble rendered extract timing out - escalate 30s to 60s to 90s with render_type idle0 before quitting" Key terms: before, escalate, extract, idle0, nimble, quitting, render, rendered, timing, type