-
-
Notifications
You must be signed in to change notification settings - Fork 43
[BUG] TooManyRequests when audit parameter is enabled #217
New issue
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
Comments
Since 429 is throttling in graph which we are managing in code (not forever though) can you see in the run output that it retries a couple of times before the error is thrown? |
Are you still seeing this on each run or has it improved? |
I saw this behaviour only on an initial backup, my workaround was to run an initial backup without audit, and then on subsequent runs include audit |
I found an issue with audit logs and Graph throttling while setting things up in 2.4.0 so this should be fixed in the upcoming version. You can already try the beta if you want to verify. |
Hey, I'm seeing this behavior also, here are the logs
They are a bit long! I used the pipeline without audit for two weeks, and then decided to try adding I will try the beta (2.4.0b6) and report back |
Using 2.4.0b6 fixed it for me ;) |
I can confirm it fixed it also for me! ;) |
Describe the bug
Two different tenants are getting "TooManyRequests" during the backup in the past two weeks, if the audit parameter is specified. Not on every run, but often 8 out of 10 runs.
To Reproduce
Steps to reproduce the behavior:
Add the audit parameter to the backup.
Expected behavior
A clear and concise description of what you expected to happen.
Retry or ignore the error.
Screenshots
If applicable, add screenshots to help explain your problem.
Run type (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: