X_SCRAPE_WEDGED
Means
the browser stopped answering and was killed
Typical cause
retryable. No browser activity at all for watchdog.idleMs, so the watchdog killed the process and closed the browser — an attached one too. The session went with it
Fix
raise watchdog: { idleMs } on the scrape() definition if the site is genuinely this slow, or call page.activity() from the channel the framework cannot see (your own CDP session, a warm-up), otherwise re-run — the browser was closed and its session is gone