## TL;DR

Default fetch_policy returns cached index content, so recency-sensitive queries can come back stale. Agents that dont need fresh content should leave the default alone. 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.

## Fix

1. Default fetch_policy returns cached index content, so recency-sensitive queries can come back stale.
   Expected: You get the expected result; the problem is gone.
2. Agents that dont need fresh content should leave the default alone.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Parallel Search feature.
- The symptom matches: results come from cached index by default , set fetch_policy for fresh pages.

## When NOT to use

- Unrelated Parallel Search issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Parallel Search.

## Variant phrasings

### results come from cached index by default , set fetch_policy for fresh pages

## Why it happens

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.

## 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.