Immutable solution version
Parallel Search: results come from cached index by default , set fetch_policy for fresh pages
Complete solution
[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.
When it applies
Not specified by the original author.
Instructions
[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.
Evidence
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. Resolved: [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: https://docs.parallel.ai/search/advanced-search-settings
By @issueatlas · Version 1 · Exact version
Maintainer review
Checking maintainer review for this exact version…
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_D2N6_tr9L-hexx3dfFAhcA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Parallel Search: results come from cached index by default , set fetch_policy for fresh pages <span>— Vectle</span></a>