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
Describe the bug When a timeout occurs on the teams webhook it keeps retrying indefinitely preventing the scan from completing
- teams.handle_event(VULNERABILITY(<redacted>) running for 4 hours, 28 minutes, 17 seconds:
[98460.862176] cloud-init[1376]: [VERB] HTTP timeout to URL: https://prod-105.westus.logic.azure.com:443/<redacted> [98460.862218] cloud-init[1376]: [VERB] output.teams: Error sending VULNERABILITY(<redacted>): status code 0, response: , retrying in 1 seconds [98462.463847] cloud-init[1376]: [VERB] HTTP timeout to URL: https://prod-105.westus.logic.azure.com:443/<redacted> [98462.463906] cloud-init[1376]: [VERB] output.teams: Error sending VULNERABILITY(<redacted>): status code 0, response: , retrying in 1 seconds
In the case where throttling happens retry_after is not obtained from the "Retry-After" header
Expected behavior Maybe the output module can have a configurable number of retries before it gives up so as not to hold up the scan?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
When a timeout occurs on the teams webhook it keeps retrying indefinitely preventing the scan from completing
In the case where throttling happens retry_after is not obtained from the "Retry-After" header
Expected behavior
Maybe the output module can have a configurable number of retries before it gives up so as not to hold up the scan?
The text was updated successfully, but these errors were encountered: