[Discovery] Discovery Schedules with multiple credential aliases might not be workingIssue When we have multiple credential aliases defined and if we use the same in discovery schedules, it might not use the right credentials. Scenario: Create a credential alias (alias1) and put it into discovery schedule (DS1). Run discovery and confirm it succeeds.Create another credential alias (alias2) and put it into another discovery schedule (DS2). Run discovery and confirm it succeeds.Now, create another discovery schedule (DS3) and put both aliased above into it. Run discovery and confirm it fails. Since both the aliases exists we expect the DS3 should work with either alias1 or alias2. But this doe snot happen.ReleaseInstance with Discovery enabled.CauseThis is expected behavior as per design. The design is as below: If we check the documentation- Credential aliases for Discovery, it clearly mentioned that Credentials must match all credential tags.Based on above ideally the credential aliases should satisfy as below: The credentials aliases are intended for the alias credentials but not for the different credentials. Please see below example:If you have credential A, and it is a member of Alias B and C.B and C have other credentials as well, but you want a schedule to ONLY use credential Aif you put aliases B and C on a schedule it will only use credential AThe credentials given in "Credential Alias" should be an AND among all the credentials but not OR. So in this scenario, the system will look for a credential with combination of alias1 and alias2 and that does not exists. This is the reason it falls into regular credentials search method.To confirm the behavior, you can check the related ECC Queue XML and look for the parameter name="credential_tag" Sample looks like parameter name="credential_tag" value="alias1,alias2"/> ResolutionMake sure to have the complete alias defined for the attached credential alias on discovery schedule.Related LinksCredential aliases for DiscoveryHow credential aliases work