Changes Not Picked Up When Promoting Scoped App Across Instances

[jmiskey]

We have a Scoped App that among other things, has the following:

- Two Catalog Items (let's call them CatA and CatB)

- One Flow (let's call it FlowA)

Both Catalog Items were using the same Flow.  However, this was not working right, as the Catalog Items have different variables, so while the FlowA works just fine in CatA, it does not work properly for CatB since CatB has different variables.

So I went into our Dev environment and I created a copy of FlowA and called in FlowB, and made the necessary edits so that FlowB works for CatB.  I then went to the Catalog Item, and updated the Flow field for CatB to use FlowB instead of FlowA.  I ran a few tests, submitting new records for CatB, and it was correctly running FlowB.  Once I confirmed everything was working correctly, I published my changes from Studio.

Then I went into our Test environment, and found my Scoped Application under System Applications -> My Company Applications, and installed the newest version I just created.  However, it seems not all the changes were promoted.  The new flow (FlowB) shows up just fine in Test.  But when I open the "CatB" Catalog Item, it still shows "FlowA" in the Flow field instead of "FlowB", even though if you look at it in Dev, it clearly shows "FlowB" in this field.  Note that I also confirmed that both these Catalog Items and Flows exist in the Scoped Application (and not in the Global Application).

What could cause something like this to happen?

Why would certain changes not be caught when promoting the Scoped Application across instances?

Thanks

[jmiskey · Accepted solution]

Found the issue - skipped updates!

There is a KB article on it here (and how to fix it): https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0690146

I wish it was more evident and told you it was skipping updates, like it they do when promoting Update Sets.

I guess I will just have to follow the steps in that article every time I do this.