Error while committing update set: Scope mismatch even though both are Global

[swethav17730498]

Hi Community,

I’m facing an issue while trying to commit an update set in my target instance.

• Update Set Name: DemoV1
• Source Instance: Update set was created in Global scope.
• Target Instance: I am previewing and committing in Global scope as well.

However, I’m getting the following error:

Cannot commit Update Set 'DemoV1' because:
Update scope id '06a71b1367e4130051c9027e2685ef1e' is different than update set scope id 'global'.
Resolve the problem before committing.

I’ve verified that:

• The update set’s Application field is set to Global.
• My current scope in the target instance is Global.

Has anyone encountered this issue before?
Why is ServiceNow still detecting a scope mismatch even though both are Global?
What’s the best way to resolve this without breaking dependencies?

Any guidance or best practices would be greatly appreciated!

[Bert_c1 · Accepted solution]

Open the update set on the instance it was created on. Add "Application" field to the related list of updates and find those not in Global. Create a new update set in the desired application scope, and move those updates to the new Update set. Complete the new update set and promote both to the new instance, and commit.  The update set can be changed after opening the update is the wrong scope.

[swethav17730498]

Hi @Bert_c1 ,

What if I directly changing the application scope from customer updates? will that work?