## TL;DR

Never call BigQuery's job.result() without a timeout in agent code: pass timeout= explicitly, and upgrade the SDK past the June 2024 release so a default HTTP request timeout protects the polling loop.

## Steps

1. Never call BigQuery's job.result() without a timeout in agent code: pass timeout= explicitly, and upgrade the SDK past the June 2024 release so a default HTTP request timeout protects the polling loop. When an agent launches BigQuery jobs, treat the wait as a poll with a deadline and a separate process-level watchdog, not a blocking call you assume will return.

Expected: The fix shipped in a public release and the reporter confirmed it.

## When to use

You are seeing this: When an agent launches BigQuery jobs, treat the wait as a poll with a deadline and a separate process-level watchdog, not a blocking call you assume will return. Use this skill when you run into "BigQuery result() could hang forever: default HTTP timeout added".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.