404 error subscription not found by pattern Azure Datacenter discovery while runnning cloud schedule ,azure cloud discovery

[shivambitanwar]

Hello Experts,

we have enabled Azure cloud discovery of root management group  in our prod environment. Activated the property glide.discovery.cdu.auto_refresh_sub_accounts_and_ldcs  but still its running Azure datacenter discovery for subscriptions that have been deactivated in azure. Getting a lot of 404 subscriptions not found errors for this pattern:Azure Datacenter discovery . How to deal with this situation. My understanding is subscriptions got discovered when they existed but now it has been deleted. so it should not try to discover datacenters for these subscriptions. 

However, thats not the case, it is considering these non-existing subscriptions and throwing erros.  my question is can this be automatically handled that if the subscription is not found in azure , it should not be part of Cloud Discovery running on management group? . 

Error details : 

 Status: 404 Response: {3} (script_include:AzureApiCommand; line 137). Custom operation Failed to run script due to the following error: JAVASCRIPT_CODE_FAILURE: com.snc.sw.exception.

If i try to access the said subscription via POSTMAN i get the same error, 404 subscription not found

[shivambitanwar]

@Hardik Benani  Looking for some help here. 

[Hardik Benani]

@shivambitanwar : The Pattern goes and find the active subscription based on the access it has. In your case it should find only the ones which are in azure and it has access to. 

1. Can you once try deleting those non-existing subscription and it's schedule from ServiceNow and re-run the discovery.

2. I will have to check the pattern what it searches for, can you paste the pattern logs here where we see the errors?

Also as ram said, make sure those inactive subscription are not a part of Azure management group.

[shivambitanwar]

we have a set of 800 subscriptions some of them with same names, its so hard to filter them out from cloud schedule as there are no filtering with help of sys id or object id .

Also this becomes a regular process whenever a subscription is deactivated in azure i have to manually exclude them.

error details--