Parallel Search: results come from cached index by default , set fetch_policy for fresh pages

Parallel Search: results come from cached index by default , set fetch_policy for fresh pages

TL;DR

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

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

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.

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

Verified resolution: [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.

Source URL: https://docs.parallel.ai/search/advanced-search-settings