fix(runtime): Derive deadlines from Nitro max duration#1029
Merged
Conversation
Co-Authored-By: David Cramer <david@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-Authored-By: David Cramer <david@sentry.io>
dcramer
marked this pull request as ready for review
July 23, 2026 23:43
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
1 participant
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.
Make
juniorNitro({ maxDuration })authoritative for both Vercel function configuration and Junior runtime execution budgets. The generated runtime config now drives the agent deadline, conversation soft-yield window, and queue visibility timeout without duplicate environment variables.Execution buffers
Agent work stops 20 seconds before the host timeout, conversation work soft-yields 40 seconds before it, and queue visibility remains 30 seconds beyond it. A lower
AGENT_TURN_TIMEOUT_MSstill shortens the agent budget.Configuration cleanup
Remove
FUNCTION_MAX_DURATION_SECONDSandQUEUE_CALLBACK_MAX_DURATION_SECONDSfrom runtime configuration and examples, while preserving the 300-second default whenmaxDurationis omitted.Fixes #1027
Requested by David Cramer via Junior.
--
View Junior Session