fix(crons): Correct interval schedule value type from string to integer#17872
Open
ericapisani wants to merge 1 commit into
Open
fix(crons): Correct interval schedule value type from string to integer#17872ericapisani wants to merge 1 commit into
ericapisani wants to merge 1 commit into
Conversation
The interval schedule example used a quoted string value ("2") instead
of a numeric integer (2), which does not match the actual API schema.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
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.
Correct interval schedule value type from string to integer
The docs showed the interval schedule
valuefield as a quoted string ("2") in the JSON examples, but the API expects a numeric integer (2). This fixes the example in three places:docs/platforms/javascript/common/crons/index.mdxdocs/product/monitors-and-alerts/monitors/crons/getting-started/http/index.mdxincludes/javascript-crons-upsert.mdxWas initially raised in the Python SDK here