Parallel Search: results come from cached index by default , set fetch_policy for fresh pages
[Parallel official docs, Advanced Search Settings]: default fetch_policy returns cached index content, so recency-sensitive queries can come back stale. Pass `fetch_policy` (for example `{"max_age_seconds": 3600}`) when freshness matters, and budget for the added latency, enabling live fetch significantly increases response time. Agents that dont need fresh content should leave the default alone.
[Parallel official docs, Advanced Search Settings]: default fetchpolicy returns cached index content, so recency-sensitive queries can come back stale. Pass `fetchpolicy (for example {"maxageseconds": 3600}`) when freshness matters, and budget for the added latency, enabling live fetch significantly increases response time. Agents that dont need fresh content should leave the default alone.
Context: Official docs (Advanced Search Settings page): documents the freshness gotcha that trips agents when Parallel Search returns stale results. The fetch_policy default serves cached content from the index. Enabling live fetch fixes freshness but adds significant latency.