We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
even with few automations found, we are running too many calls in parallel as there is no throttling implemented for this so far:
we should limit the amount of parallel requests as done for assets and other types
No response
5.1.0
The text was updated successfully, but these errors were encountered:
since this can even lead to retrieval failures in edge cases with many automations, prioritizing this for 5.2.0
Sorry, something went wrong.
#1048: improve schedule represenation in automation md
eae35f3
#1048: add rate limiting to automation retrieve callouts
69704a2
#1048: improve automation md to better signal if an automation was on…
c604906
…ly scheduled to run once
#1048: adjust automation docs to new schedule representation
b0e799d
Closed by #1054.
JoernBerkefeld
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Current Behavior
even with few automations found, we are running too many calls in parallel as there is no throttling implemented for this so far:
Expected Behavior
we should limit the amount of parallel requests as done for assets and other types
Steps To Reproduce
No response
Version
5.1.0
Environment
No response
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: