Wrong sys_id being captured in update set

[spike]

I'm having a problem with sys_ids being "wrong" in my update sets.

The premise is this:

I'm creating new catalog items using the Catalog Builder and capturing those changes into an update set. My admins then try to migrate that update to the next environment and I'm told it fails due to errors with missing records. On investigation I can see the individual customer update records have different sys_ids for the same thing.

For instance, the sys_id for my published RoboForm Access SR in Dev is afd75c4a1bf789506ccca792f54bcb0a.

In the update set that creates this, I can see that reference:

<sys_id>afd75c4a1bf789506ccca792f54bcb0a</sys_id>
<sys_mod_count>5</sys_mod_count><sys_name>RoboForm Access</sys_name>

And some of the updates list the correct sys_id for the SR:

<cat_item display_value="RoboForm Access">afd75c4a1bf789506ccca792f54bcb0a</cat_item>

But, and here's the kicker, 6 out of the 17 customer updates captured on that update set have the wrong sys_id:

(not all 6 listed, 3 different sys_ids reported)

<sc_cat_item display_value="RoboForm Access">b91a180e1bf789506ccca792f54bcb46</sc_cat_item>
<sc_cat_item display_value="RoboForm Access">ccba508e1bf789506ccca792f54bcb1f</sc_cat_item>
<sc_cat_item display_value="RoboForm Access">b4799cca1bf789506ccca792f54bcb90</sc_cat_item>

What the actual?

The only reference I can find to these sys_ids is in DELETE records in the update set (and my admins tell me to move these delete records to the default update so they can be ignored.

I am completely lost here. Any help anyone can offer would be most appreciated!

[spike]

I'm wondering if this might be a bug of sorts. I'm using the Catalog Builder to build the Service Requests. At the end of that process the SR is "Published." This takes it through a number of stages (checked out, draft, published (maybe something else)).

I wonder if it's the SR moving through this process that is causing the sys_id to change each time it's moved to the next stage. As a result the update set is capturing a different sys_id as it's capturing the change.

I've no proof of this though. It's just a thought and I'd welcome any input..

[spike · Accepted solution]

Turns out it is a bug:

https://community.servicenow.com/community?id=community_question&sys_id=291ef164db8019500d48db85ca961936