Edge case AWS Cloud Discovery configuration can cause StackoverFlow error - Known Error

Edge case AWS Cloud Discovery configuration can cause StackoverFlow error Description When following the configuration in the reproduction steps you note that StackOverflow error is reported in ecc_queue input or MID server logs.

Steps to Reproduce

- Configure Parent Account P with Accessor as Member Account 1 - Configure MID server with IAM instance profile Member Account 2 - Run discovery on P

Workaround 1. Open the `ecc_queue` record.

2. Open the XML.

3. Copy the `correlator` value.

4. /discovery_status_list.do?sys_id=

5. Identify why the impacted MID server was selected for the Discovery Status.

6. Update the Discovery Schedule MID server selection method or the MID server capabilities.

https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/mid-server/concept/c_MIDServerSelector.html

https://docs.servicenow.com/en-US/bundle/utah-it-operations-management/page/product/discovery/task/t_CreateADiscoverySchedule.html

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/mid-server/reference/r_MIDServerCapabilities.html

This problem is currently 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.