Playbooks configuration issue while moving the changes from one instance to other

[pankajxshar]

Hi , 

Lately we have been facing some issues with Playbook configurations. We have created some playbooks in our Dev instance and moved them to our higher instance, but not every changes were successfully moved. We did try to capture the missing changes separately and it worked. 

Now if we are making any changes to our Playbook and move it across it gives us an error "Couldn't find the snapshot record" for the playbook and the changes are not reflected, Moreover existing activities within the playbook also get impacted when we haven't made any changes to it. This is the first time we are configuring our playbooks in our instance. Currently we are in Xanadu version. Has anyone faced similar issues while moving playbooks across instance?

[LVdV]

We're running into the same issue. Did you create a case with ServiceNow, or find a solution?

[pankajxshar]

There is an ongoing issue with moving Playbooks changes and Servicenow working towards fixing it. Please try the below workaround to resolve your issue, 

Option A.

Will populate Inserted / Updated / Deleted / Collision / Total fields but is has more steps.

1. Upload the update set.
2. Go to sys_remote_update_set table and open the upset set record.
3. Go to Customer Update tab and open the sys_pd_process_definition_ # # # record.
4. Copy the entire payload (to be used in step 😎
5. Go back to the Retrieve Update Set
6. Click on 'Preview Update Set'(this step will corrupt the payload)
7. Go to Customer Update tab and open the sys_pd_process_definition_ # # # record again.
8. Replace the payload with what was originally copied from step 4. Click on Update.
9. Go back on the Record Update Set.
10. Click on "Accept remote update".
11. Click on "Commit Update Set".
    
    

Option B.

This unfortunately will not update the Inserted / Updated / Deleted / Collision / Total fields but has less steps.

1. Upload the update set.
2. Go to sys_remote_update_set table and get the sys_id of the update set.
3. Go to 'Scripts - Background' and run as admin with the appropriate sys_id:
          

var gr = new GlideRecord('sys_remote_update_set');
          gr.addQuery('sys_id', '**insert sys_id here**');
          gr.addQuery('state', 'loaded');
          gr.query();
       if (gr.next()) {
          gr.setValue('state', 'previewed');
          gr.update();
      }

1. Go to sys_remote_update_set table and open the update set
2. Click on 'Commit Update Set'.

Please mark the answer "Accept as solution" if it has helped you.

[mhorky]

Thank you for providing the Workarround. We went with Option A and can confirm it worked.

Do you by any chance have a link to a Known Issue?

We also raised a ticket towards ServiceNow. But yet no reply.

[Diogo Ramos]

Latest feedback I got : 

PRB1839341 - Update Set with Playbook change failed to install

Targeted version(s) Xanadu Patch 8,Yokohama Patch 2,Zurich

KB KB1891818 : Update Set with Playbook change failed to install showing Invalid Preview error. - Known Error