Workflow and Flow are not working after cloning

[Community Alums]

Hello all,

We have recently moved to a new ServiceNow instance. For that we have cloned from our old ServiceNow instance to the new instance PROD.

After this our flows for requested items/change requests which was created in old instance are not working as these were excluded while cloning.

So is there any fix for this, as we cannot clone again.

Thanks in advance

Anand

@Manmohan K , @Ankur Bawiskar , @Community Alums , @Karan Chhabra6 , @AndersBGS , @Sandeep Rajput , @Mark Roethof , @Amit Gujarathi , @Riya Verma 

[Ankur Bawiskar]

@Community Alums 

if you excluded them then they won't come to your instance.

you can capture those in your update set in source and commit that update set in target

[Community Alums]

Hello @Ankur Bawiskar ,

How we can capture currently executing workflows (wf_context table) which are attached to requested items and change requests in update set.

Please suggest.

Thanks

[Mark Roethof]

Like I mentioned, there are several tables involved. Not just the wf_context table. Only exporting/importing these, or adding it to an update set, is by far not enough.

For example have a look at wf_context records manually. You will notice then that more tables are involved, wf_executing, wf_history, wf_transition_history, etc, etc..

Kind regards,
Mark

[Mark Roethof · Accepted solution]

Hi there,

That is expected behavior. Usually you won't clone all the tables involved for active workflows and flows.

With such migrations, it's up to your company itself to define a strategy. For some customers I see that they are handling existing/old tickets on the old environment/old product, and only handling new tickets on the new environment. Or what I also see customers do, is closing old tickets and raising a new one. Can be a bit painful/time consuming for a few days, though then its permanently fixed. 

Kind regards,
Mark