Default SLA flow sync up issue

[BAK2211]

Hello Everyone,

Hope you are doing good.

Currently we are using the CICD gitlab process to migrate our customizations. Code commit in dev instance to source control (gitlab) and migrating to higher instances by running the automatic pipeline.

Earlier when any records is created (inc, case) ,based on condition of the SLA either response or resolution SLA was missing on the record. So for this issue we raised a case to servicenow and they identified the root cause and provided the workaround.

As per them its a flow sync up issue and for that you need to go individual instance and edit the default sla flow and publish it again. After this both target and response SLA gets attached and working as per process.

But now what happening is, this issue coming all the time when we have a deployment for global application for any changes related to global scope (the deafult sla is part of global app and we are capturing the changes in custom created global app for code movement). 

so anyone face similar kind of flow sync up issue and do we have any workaround ? Because it is not good idea to refresh the flow all the time in all instances(including prod) when we will have a deployment of global application. 

Thanks,

Akshay

[BAK2211]

If you want more info (even for update set code movement ) ,you can see the below KB from servicenow.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1117831

But I am looking for Permanent solution. Because we have number of deployments in prod. 

Thanks,

Akshay

[ersureshbe]

Hi, I suggest - use same OOB flow and duplicate the OOB flow. You change the item what recommended by ServiceNow in duplicate OOB flow. Map that flow to the SLA configuration and test it.

[BAK2211]

Due to this we find out that the flow got broken and did export and import it in affected instance. Also the sys_complex_object record moved to the global scope.