Repository navigation
Whats New for the week of 09-28-2026 - #1280
Merged
Merged
Conversation
Lightsage docs evalsLightsage could not queue docs evals for this PR. Docs URL: https://vapi-preview-01a0fd84-17a5-702d-980f-a49127d6a88c.docs.buildwithfern.com |
amanda-vapi
approved these changes
Oct 2, 2026
Contributor
|
🌿 Preview your docs: https://vapi-preview-01a0fd84-17a5-702d-980f-a49127d6a88c.docs.buildwithfern.com |
scott-lowe-vapi
added a commit
that referenced
this pull request
Oct 6, 2026
## 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 `latencyExpectations` and `latencyEvaluations` fields through the nightly spec update; this PR covers the guides. - **Simulations advanced**: new **Set latency limits** section and card: - Dashboard and cURL setup; - the `turn`, `model` and `voice` metrics and the four aggregations, including that `p95` equals `max` under 20 turns; - required versus optional limits; - when limits are skipped (chat mode, GPT-Live assistants under test) and that a voice run with no measured turns fails; - reading results in the run details and through `results.latencyEvaluations`; - two troubleshooting rows. - **Simulations overview**: the scenario definition, the "how it works" paragraph and the Evals comparison table now mention latency limits next to structured outputs. - **Manage simulations**: run results mention latency results and `latencyEvaluations`, "Design evaluations" points to latency limits, and the voice-or-chat table gains a "Gate on response latency" row. - **GPT-Live testing**: notes that latency limits are skipped when the assistant under test uses GPT-Live. 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 check` with 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](https://claude.com/claude-code)
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
2 participants
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.
Description
Testing Steps
fern docs devor navigate to preview deployment