Flow is suspended due to Deleted DLP Policy

(0) Share

Report

Posted on by Matt Collinge

Please help if you can. 🙏

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.

Remove-DlpPolicy for the Policy that is causing the issue

Any suggestions would be greatly appreciated.

Categories:

Security

I have the same question (0)

All responses (1)

Answers (0)

Matt Collinge 45 on at

Like (0)

Report
Copy link

Link copied!
Copy Each Flow - Save As New Flow Names

Remove all links to other Child Flows

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? Yes No