about a flow deactivation

[Mamidi]

Hi all,

actually i deactivated a OOB flow in EAM  which i just wanted to edit that's why i did that and that too in vendor instance and we tried to install and uninstall so that the spokes will get like that and the flow is in asset management common application and a security admin also can not able to make the active true it is showing security prevention i don't know why and i have admin role for your information and we know that when i copy and make the exact same it won't work as  OOB flow as it won't bind and wired that much strongly with the system as a OOB flow as it has a similar visual design but the back thing has more to do i guess ,so can you please help me to make it activate

[Mamidi]

Hi @Ankur Bawiskar then the solution above will work or not by delaying the update in customer updat table will it works in vendor instance

[Mamidi]

@Ankur Bawiskar 

Thanks for sharing the KB — agreed, that’s the recommended approach for long-term customization (copy the flow + keep OOB deactivated). In my case I’m only trying to restore the original OOB behavior, so deleting the sys_update_xml override (which contains active=false) simply reverts to the base flow and is it safe. If anyone has other supported workarounds (ex: “Revert to Base System”, scope-based fix, or a cleaner way to re-enable without Support), please suggest.

[Ankur Bawiskar]

@Mamidi 

you can try that option.

[Mamidi]

@Ankur Bawiskar yes i tried that but its not activating the flow in dev instance i tested if because i don't want to create another mess but in that itself its not working so i agree to your kb article but can i have any other solutions if has let me know it thank you for your time to answer.

[Ankur Bawiskar]

@Mamidi 

in this case please proceed with raising case with ServiceNow.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏