The issue only happen when a flow calls "Run Child Flow" action.
But it was working few weeks ago.
If I remove the action "Run Child Flow", the error message go out.
I tried to add a connector to the DLP in admin console, but there is no connector called "Flow", that should be the same type of the action "Run Child flow".
Someone can help?
Thanks for the answer...
Actually, the child flow is tested and turned on, without errors or policy broken.
It driven me to think that there is a problem with the action "Run Child Flow", or a special policy to enabled/disabled this kind of solution.
PS: All the flows is inside the same solution in the same environment.
I worked around this issue eliminating the 'Run a Child Flow' from the flows.
When the actions of child flow is running inside the parent flow, the DLP violation does not happens.
Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
Many congratulations to the Season 1 2021 Flownaut Crew!
Check out our new profile badges recognizing authored solutions!
Check out the community blog page where you can find valuable learning material from community and product team members!