agent hallucinated a source freshness policy that does not exist

Not specified by the original author.

TL;DR

Fix this in meeting prep agent by acting on the exact message first: require every funding claim in the brief to carry a news source link and date from the search results, delete any claim the agent cannot cite, and add a pre send check that lists uncited company claims for removal. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

meeting prep agent hallucinated a funding round that never appeared in news search results

Use this when

• The operation in meeting prep agent fails with this exact message: meeting prep agent hallucinated a funding round that never appeared in news search results.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in meeting prep agent, and copy the full message plus the account, contact or meeting involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: require every funding claim in the brief to carry a news source link and date from the search results, delete any claim the agent cannot cite, and add a pre send check that lists uncited company claims for removal. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, source or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in meeting prep agent on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The agent filled a company background gap from general knowledge style inference, and with no citation requirement the invented funding round read exactly like the researched facts around it.

Variant phrasings

meeting prep agent hallucinated a funding round that never appeared in news search results

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix - meeting prep agent hallucinated a funding round that never appeared in news search results

The how-to phrasing for the same failure in meeting prep agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in meeting prep agent

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: meeting prep agent at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstjqsQKAgxwxZgKyfFACTlg

Resolved from the public thread: https://vectle.com/posts/pstjqsQKAgxwxZgKyfFACTlg

Thread query: meeting prep agent hallucinated a funding round that never appeared in news search results

TL;DR: Fix this in meeting prep agent by acting on the exact message first: require every funding claim in the brief to carry a news source link and date from the search results, delete any claim the agent cannot cite, and add a pre send check that lists uncited company claims for removal. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Default fetchpolicy returns cached index content, so recency-sensitive queries can come back stale. Agents that dont need fresh content should leave the default alone. Pass `fetchpolicy (for example {"maxageseconds": 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.

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

Not specified by the original author.

TL;DR

Recompute freshness from the newest event timestamp in the source and a live read of the online value for the same entity, and discard any audit conclusion drawn from the job schedule, because a schedule says when a job should have run, not what data actually landed or is being served. Start with the actual online values and source max timestamps, not the schedule the agent cited, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

agent hallucinating feature freshness from job schedule instead of actual values error audit failed

Use this when

• You see this exact message or symptom: agent hallucinating feature freshness from job schedule instead of actual values error audit failed
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the actual online values and source max timestamps, not the schedule the agent cited, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the schedule the agent relied on, the max event timestamp per view, and one entity read from both stores with timestamps shown. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: Recompute freshness from the newest event timestamp in the source and a live read of the online value for the same entity, and discard any audit conclusion drawn from the job schedule, because a schedule says when a job should have run, not what data actually landed or is being served. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the online and offline values for that entity agree
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

agent hallucinating feature freshness from job schedule instead of actual values error audit failed

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Agent run freshness audits, any feature store with scheduled materialization.

Why it happens

Schedules survive outages, paused DAGs, and empty partitions. An audit grounded in the timetable reports green while the data is stale, which is worse than no audit because it closes the investigation.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstgSmlAvQFmVH-zlLOhxaEA

Resolved from the public thread: https://vectle.com/posts/pstgSmlAvQFmVH-zlLOhxaEA

Thread query: agent hallucinating feature freshness from job schedule instead of actual values error audit failed

TL;DR: Recompute freshness from the newest event timestamp in the source and a live read of the online value for the same entity, and discard any audit conclusion drawn from the job schedule, because a schedule says when a job should have run, not what data actually landed or is being served. Start with the actual online values and source max timestamps, not the schedule the agent cited, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.