Hi,

Yes, basically.

If you have an update set that has moved up through ALL the environments and is now on Prod and committed, but left as Complete. If/when Prod is ever cloned somewhere else, that update set will show in the retrieved update set list and appear as if it has not been committed, when it really had. It can cause confusion and people to recommit sets, when they aren't needed. And if recommitted, cause issues within the instance.

Having them set as ignored, prevents them from loading back in to the retrieval process.

Repeated explanation here though just in case you want to see it from others, like SN staff: https://community.servicenow.com/community?id=community_question&sys_id=852c4365db9cdbc01dcaf3231f96...

Please mark reply as Helpful/Correct, if applicable. Thanks!