Fix video agent API evidence collection and answer quality - #22
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A production request for “suggest the top use cases of gpt 6 astra” exhausted the research window without usable transcript evidence and returned promotional discovery text as a partial answer. Local reproductions also exposed extra search planning, transcript selection in separate waves, and invalid structured model output.
Changes
NO_CONTENT_EVIDENCEfallback when content analysis fails, instead of synthesizing recommendations from titles and descriptions. Track transcript attempts synchronously so deadline aborts cannot race failure recording.The 60-second deadline and 20-second finalization reserve remain. The proposed public response redesign is separate from this fix.
Validation
The final timeout race guard was validated with a regression test after the live runs. These timings demonstrate successful local runs, not a latency guarantee. Source claims remain attributed rather than independently verified. Production verification follows merge and deployment.