After Cloning Servicenow instance facing Flow designer issue.

[Rahul63]

Hello everyone, We have cloned our ServiceNow instance with Production. After cloning I'm facing below issue for all the flows & subflows. Error :- "Your flow cannot be found. Flow sys_id:nnot invoke "com.glide.flow_design.action.model.Flow". 

Also, after creating a new flow & selecting a trigger getting "Internal Server Error".

 Thanks in advance.

[Ankur Bawiskar]

@Rahul63 

Is this happening for only 1 flow or all flows?

If for all then did you try creating a fresh flow and see?

If issue still persists then raise a case with ServiceNow.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Rahul63]

Hello @Ankur Bawiskar , Getting this error for all the flows & sub flows. Also while creating new flow & selecting a trigger it shows "internal server error". 
Thank you for your response.

[Ankur Bawiskar]

@Rahul63 

Raise as case with ServiceNow and do let us know the updates.

[Robert H]

Hello @Rahul63 ,

Did you select "Exclude tables specified in Exclusion list" when requesting the Clone? And if so, did you add any "Exclude tables" that are related to Flows?

Regards,

Robert

[Rahul63]

Hello @Robert H , I have additionally added some tables to the exclude & preserve list which are following:- 

• sys_user
• sys_dictionary
• sys_user_has_role
• sys_user_role
• sys_user_group
• sys_user_grmember
• sys_group_has_role
• sys_user_role_contains
• sys_group_has_skill
• sys_user_group_type
• sys_user_group_visibility
• customer contact 
• sys_certificate
• sso_properties
  
  Do you think from any of the above table causes any issues for the flow?