Hi there,

Unmanaged this case indeed grow extremely large and make it a lot more difficult when deploying or even accidently opening the wrong retrieved update set.

What I usually do at customers is implement scheduled Instance Scan Checks, one of them checking for uncommitted update sets in production. This way the customer is noticed immediately and can take action. For example by deleting the retrieved update set (which is fine to do!) + changing the state of the local update set on the source instance to ignore so it won't be retrieved again.