Repository navigation
docs(serverless): document /status-sync, the 570000 ms wait limit and gated Hugging Face access - #966
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
… gated Hugging Face access
nick4fake
force-pushed
the
bohdanyurov/con-1331-status-sync-gated-models
branch
from
November 13, 2026 00:05
90d0ecb to
e93a58f
Compare
lavanya-gunreddi
approved these changes
Nov 13, 2026
This branch was successfully deployed
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.
Three gaps that agents and users hit while running serverless workloads:
/status-synchad no documentation. It holds the request until a job submitted with/runfinishes or the wait runs out (default 90 s,?wait=1000-570000 ms) and returns the same body as/status, so clients don't have to poll/statusthrough a long cold start. New section in the operation reference, after/status./runsyncwait range said 1000-300000 ms. The API accepts up to 570000 ms; a larger?waitis rejected withwait is invalid; must be between 1000 and 570000.modelparameter section now say so.