Veracode Scan Summary Integration Failure Due to 429 ErrorIssue The Veracode Scan Summary Integration fails with a 429 error. HTTP 429 errors occur when Summary Integration and Link Projects integration run concurrently in Veracode integrations. Additionally, occasional response timeout failures are experienced ReleaseAll Version of ServiceNow.CauseThe service interruption is most likely due to a combination of scheduling conflicts between Veracode integrations and insufficient response timeout settings for Veracode API callsResolutionImplement Schedule Adjustment: Update the scheduled run time of "Veracode Categories Integration" to 9:30 AM (previously 12:30 PM). Note schedule varies per instance. Increase Response Timeout: Change global system properties:a. Set glide.http.outbound.max_timeout.enabled to falseb. Set glide.http.outbound.max_timeout to 60 seconds Test the solution: Implement the changes in a sub-prod instance.Monitor for any occurrences of HTTP 429 errors or response timeout failures.If issues persist, further troubleshooting may be required. Verify resolution: Confirm that Veracode integrations run smoothly without conflicts or timeouts.Ensure that Summary Integration and Link Projects integration can run concurrently without errors If the issue persists after implementing these steps, additional investigation and troubleshooting may be necessary.Please test this solution in a sub-prod instance. If this does not resolve your reported issue, please reject the solution and we will continue to troubleshoot. If your issue is resolved, please feel free to close this case.Note: Veracode is working on releasing a new reporting API for scan summary information, which may resolve this issue.