We have Flows that are suspended due to a DLP Policy that has been deleted. I have raised a support ticket on the 10th October, but have not yet received a fix.
Details:
Using the CoE Toolkit 'DLP Impact Analysis' app I had cloned a baseline DLP policy, added some further restrictions specifically for the Default Environment and then applied the Policy to the Default Environment ONLY.
After this there were certain Flows in the Dev, UAT and Prod environments that were suspended. These environments were not assigned to the policy.
I then deleted the Policy, yet we still have Flows that are suspended due to the DLP Policy.
Even if I try to use PowerShell to remove the Policy, it can't be found, yet whenever trying to Turn On the Flows, they are suspended.
Set all Connection References Again - Do this for all Flows that are Child / Parent
Make Sure all Flows are not using Run-Only-User
Re-Add All Child Flows to each of the Flows
I have deployed the solution for testing next week, so I will see how that goes.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
43
Share
Report
All responses (
Answers (
