- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-04-2023 02:22 AM
In Vulnerability Response, the scheduled job "Tenable.io Fixed Vulnerabilities Integration" is failing and not creating vulnerable items in servicenow. And it is showing error "Encountered error running the integration. Error: Invalid response code 429 received from TenableIOVulnerabilitiesIntegration: Too many requests, Cannot create more than one export status request at same time."
How can I fix this issue?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2023 07:28 AM
We just fixed this same problem. You probably have a stuck export job on the Tenable side. You cannot see the job in the exports dashboard because Tenable doesn't think that's a useful feature. Instead, you have to use the API. Exports (tenable.com) Here are the steps I took:
1. Use the Get vuln export jobs (tenable.com) API and look for jobs with a status "PROCESSING" and record the UUID. you can also convert the "created" time from EPOCH time to see when the job started. I recorded "PROCESSING" jobs that were created around the time of our last good integration run.
2. Use the Cancel vuln export (tenable.com) API and insert your UUID from the previous step.
3. Repeat until you have cancelled all the jobs you think are from your ServiceNow integration.
4. Test your integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2023 07:28 AM
We just fixed this same problem. You probably have a stuck export job on the Tenable side. You cannot see the job in the exports dashboard because Tenable doesn't think that's a useful feature. Instead, you have to use the API. Exports (tenable.com) Here are the steps I took:
1. Use the Get vuln export jobs (tenable.com) API and look for jobs with a status "PROCESSING" and record the UUID. you can also convert the "created" time from EPOCH time to see when the job started. I recorded "PROCESSING" jobs that were created around the time of our last good integration run.
2. Use the Cancel vuln export (tenable.com) API and insert your UUID from the previous step.
3. Repeat until you have cancelled all the jobs you think are from your ServiceNow integration.
4. Test your integration