Qualys integration fails with 409 error codeSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The issue with Qualys Comprehensive Host Detection IntegrationEncountered an error running the integration. Error: Invalid response code 409 received from Qualys Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Qualys integrations may fail with the error : Encountered an error running the integration. Error: Invalid response code 409 received from Qualys From the node logs: 2023-11-28 16:09:02 (776) worker.5 worker.5 txid=XXXXXXX SEVERE *** ERROR *** sn_vul (VulnerabilityIntegrationController): Caught error while retrieving data, integration process VINTPRC00XXXXX Error: Invalid response code 409 received from Qualysundefined2023-11-28 16:09:02 (771) worker.5 worker.5 txid=XXXXXXX SEVERE *** ERROR *** sn_vul_qualys (QualysHostDetectionIntegration2): Invalid response code 409 received from Qualys This can happen due to one of the following reasons: 1. If the same key is used in multiple environments, or it’s trying to run multiple jobs concurrently, the Qualys endpoint can return 409 2. The API rate limit has been reached for the sliding window. Demonstrating this using an example header received from Qualys: X-RateLimit-Limit: 300X-RateLimit-Window-Sec: 86400X-Concurrency-Limit-Limit: 2X-Concurrency-Limit-Running: 1X-RateLimit-ToWait-Sec: 0X-RateLimit-Remaining: 299Transfer-Encoding: chunkedContent-Type: application/xmlSome explanations:X-RateLimit-Limit: 300 means that your subscription is configured to allow 300 calls per API calls/functions (in this example, about.php can be called 300 times, independently of the other API calls that are performed with the same account) during the sliding window provided below (X-RateLimit-Window-Sec)X-RateLimit-Window-Sec: 86400 is the sliding window (in seconds) for the parameter above. 86400 seconds is 24 hours.X-ConcurrencyLimit-Limit: 2 means you can launch the same call 2 times at the same timeX-ConcurrencyLimit-Running: 1 means only one call is currently runningX-RateLimit-ToWait-Sec: 0 means you've not been blocked, so you don't have to wait before launching a new callX-RateLimit-Remaining: 42 means you still have 42 requests available for this API call for the time that remains in the sliding windowIf for some reason you are blocked, you get a 409 HTTP error and you can figure out what is the root cause of the problem in the header or the response (either the concurrency limit reached or too many calls so you need to wait X-RateLimit-ToWait-Sec seconds). More information about the qualys performance tuning can be found here: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863634 Based on the above reasons to resolve the issue 1. Please avoid using the API key from multiple instances or please schedule the runs at different times in those instances to ensure there is no overlap. 2. For rate limiting it depends on the data that you are willing to fetch which decides the number of API calls to be made within the sliding window, this can be controlled by truncation_limit as mentioned in the KB0863634 More information on Qualys API limits: https://cdn2.qualys.com/docs/qualys-api-limits.pdf