Multiple entries of upgrade history in cloned instance but only one on source instance.Issue Monthly updates are successfully applied on all production and sub-production instances. However, on one sub-production instance, the upgrade history shows two or three entries while all other instances show only one.ReleaseQuebec and newer.CauseThe scheduled job "Check Upgrade Script (Does Nothing)" is an old job used in previous versions. The functionality of this job was moved to "Check database for possible upgrade" and the trigger type changed from "Run at System Startup" to none to prevent it from running when the instance is restarted. For some unknown reason, the trigger type was changed back to "Run at System Startup" which triggered additional upgrade checks during the monthly update. Even after cloning over the target instance, the record was preserved on the target instance because the record was modified and would trigger the multiple updates.ResolutionSet the trigger type of the scheduled job "Check Upgrade Script (Does Nothing)" from "Run at System Startup" to "None".