Discovery schedule behaving differently when left to run as per the schedule and when ran using Discover Now UI action.Issue The Discovery schedule behavior is not as expected. It creates a number of credential errors when it is left to run as per the schedule, but when it is run manually via 'discover now' we do not see these errors. When the discovery schedule is left to execute as per the schedule it throws a lot of credential authentication errors on many servers. If we examine the logs we can see that most of them are failing at WMI: Classify with the credential error.Whereas if we run the same discovery schedule manually by pressing Discover Now, then we can see that those errors are not visible anymore. And when we look at those servers that had failed before we can see that the WMI: Classify was successful with the same credential that had failed before. We can see errors like the following below in the agent logs: ReleaseAll releases where 2 Mid agents sit on the same windows server and share the CyberArk Agent.CauseDuring a recent clone, the trigger time for the same discovery schedule in UAT instance had been cloned too and this was causing the schedules to fail in both Prod and UAT instances.ResolutionThe issue got solved when the changes were made to the trigger time for the discovery schedule.