Repository navigation
Document latency limits for voice simulations - #1288
Merged
Merged
Conversation
Voice simulations can now fail when the assistant responds too slowly (VapiAI/vapi#21959, #21962, #21963; TEST-140). Add a "Set latency limits" section to Simulations advanced covering the Dashboard and API setup, the turn, model and voice metrics, the aggregations, when limits are skipped (chat mode, GPT-Live assistants) and how to read the results. Mention latency limits where the overview, manage and GPT-Live testing pages describe how a simulation is scored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lightsage docs evalsLightsage could not queue docs evals for this PR. Docs URL: https://vapi-preview-01a11374-b04e-771e-a168-40438c9b76a6.docs.buildwithfern.com |
Contributor
|
🌿 Preview your docs: https://vapi-preview-01a10f49-53e0-77f5-8ff6-5999fdcb08f6.docs.buildwithfern.com |
stephenvapiai
left a comment
Contributor
There was a problem hiding this comment.
Two suggested wording changes for the latency limits section. Each suggestion can be accepted independently.
stephenvapiai
approved these changes
Oct 6, 2026
Contributor
|
🌿 Preview your docs: https://vapi-preview-01a11374-b04e-771e-a168-40438c9b76a6.docs.buildwithfern.com |
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.
Summary
Voice simulations can now fail when the assistant responds too slowly. The feature shipped in VapiAI/vapi#21959 (API and worker), VapiAI/vapi#21962 (run results) and VapiAI/vapi#21963 (editor), tracked in TEST-140. The API reference already shows the new
latencyExpectationsandlatencyEvaluationsfields through the nightly spec update; this PR covers the guides.turn,modelandvoicemetrics and the four aggregations, including thatp95equalsmaxunder 20 turns;results.latencyEvaluations;latencyEvaluations, "Design evaluations" points to latency limits, and the voice-or-chat table gains a "Gate on response latency" row.Every behavior described was checked against the merged code: field names, the default of a required median turn latency of 1,200 ms, the 1 to 60,000 ms range, the 20-limit maximum and the skip rules.
Not included
A "What's new" changelog entry. The weekly changelog files look curated by one author (e.g. #1280), so I left the entry to the next weekly post. Happy to add it here instead.
Testing
fern checkwith the pinned CLI 5.112.0 (node scripts/fern/run.cjs check): 0 errors. The 14 warnings are pre-existing discriminator warnings in the API spec. The preview link from CI is the place to check rendering.🤖 Generated with Claude Code