Orca Integration runs for VR are stuck in "Wait complete" state if the "Run As" user is not empty.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2022 08:19 AM
Hi Team,
We are using Orca Integration for creating vulnerable items in ServiceNow. The integration runs fine if the "Run As" is empty. If the "Run As" user is selected as myself (admin) it gets stuck in "Wait Complete" and "Queued". It remains in Wait Complete unless I forcefully cancel the job. Though the substate shows to be "success". Any idea how to troubleshoot this? What could be the cause of this issue?
I have already followed the Qualys Integration setup article which is similar to the one required for ORCA integration. The scheduled job are all set.
In our case the actual requirement is different than the one I mentioned above. Actually, the "Run As" user should be a domain specific user so that the vulnerable item gets created in a domain separated manner. When I use a Domain specific user the error is different and can be checked later.
I used the "Run As" = Admin just for troubleshooting but unfortunately, even that is not working.
Can you please suggest as to where is it going wrong?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2024 06:39 AM
Hi Maloy,
How are you doing this Orca integration? Does ServiceNow offers any OOB connector or you are manually?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2025 02:56 AM
This is a custom integration, OOB is not available in ServiceNow