Fill gaps from assistant conversations: WebSocket duration and region/provider interaction - #316
Open
mintlify[bot] wants to merge 2 commits into
Open
Fill gaps from assistant conversations: WebSocket duration and region/provider interaction#316mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
kylegani
requested changes
Aug 18, 2026
kylegani
left a comment
kylegani
left a comment
Contributor
There was a problem hiding this comment.
We're doing away with providers as a choice and our scaler automatically handles scale already. Remove the references to provider.
milo157
approved these changes
Aug 18, 2026
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.
Summary
Address two recurring assistant-conversation themes where users had to infer behavior the docs did not state.
Changes
endpoints/websockets.mdx: added a "Session Duration" section explaining that WebSocket sessions are bounded byresponse_grace_period(default 900s), how to raise it, and the SIGTERM implication for custom runtimes.deployments/multi-region-deployment.mdx: added a "How Region, Provider, and Compute Interact" subsection clarifying thatregion = "global"does not override a pinnedprovideror a singlecomputevalue, showing the fallback pattern with acomputelist, and noting that changes apply on the nextcerebrium deploywithout recreating the app.Context
Recent assistant conversations repeatedly asked how long a WebSocket can stay open and whether
region = "global"auto-switches provider or GPU type. Both answers exist in the platform's behavior but were not written down on the affected pages.