Set maxSecondsBetweenMessages value for certified connectors Phase 1
#36382
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
area/connectors
davinchia
approved these changes
Mar 22, 2024
lazebnyi
approved these changes
Mar 22, 2024
bazarnov
changed the title
certified connectors Phase 1
bazarnov
changed the title
certified connectors Phase 1maxSecondsBetweenMessages value for certified connectors Phase 1
|
/approve-and-merge reason="batch changes of maxSecondsBetweenMessages in metadata.yaml files" |
|
Lets merge it |
octavia-approvington
approved these changes
Mar 26, 2024
octavia-approvington
deleted the
DanyloGL/maxSecondsBetweenMessages_value_adding_1
branch
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.
For certified connectors is requirement to have
maxSecondsBetweenMessagesset in metadata file.maxSecondsBetweenMessagesis the longest time frame (in seconds) of API requests limits reset for endpoints used by connector.What
maxSecondsBetweenMessagesvalue for the following connectors was added:maxSecondsBetweenMessages: 60. Longest time frame of limits reset is 1 minute or 60 secondsmaxSecondsBetweenMessages: 86400. Longest time frame of limits reset is 1 day or 86400 secondsmaxSecondsBetweenMessages: 86400. Longest time frame of limits reset is 1 day or 86400 secondsHow
Files
metadata.yamlfor connectors mentioned above were updated by addingmaxSecondsBetweenMessagesvalue.🚨 User Impact 🚨
No breaking changes