Loading...
Loading...
Make sure you have a cloud discovery schedule for which few sub-accounts exists. Add the system property "glide.discovery.cdu.auto_refresh_sub_accounts_and_ldcs" set to true so that all sub-accounts are refreshed in each cloud discovery preventing delay. Go to the schedule and use "Discover Now" UI link. A pop-up window will state process starting, and after some time it will end with error ""Could not redirect to Discovery status""
This problem is under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available. The possible workarounds below will not stop creation or running of discovery status, but you will not be redirected to to related discovery status: Go to Discovery Status list view and look for the schedule you are looking for. Increase the value for "glide.discovery.discover_now_timeout" to 60 or 90 secs. Ref.: Discover Now related link button giving error message "Could not redirect to Discovery status" Discovery of any CI fails with "Could not redirect to Discovery status" error when clicking on Discover Now UI action from Discovery Schedule
PRB1639913
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.