Dynamics Community Forum Thread Details

OOTB Cloud Flow is disabled because it is not used often and cannot be turned back on

My apologies if this post is in the wrong discussion thread, but this is a platform issue, and is not relevant to an "app" (eg Sales or Field Service).

Why does Microsoft disable cloud flows that have not run in X days? They are not consuming resources. Makes no sense. Especially OOTB Managed Cloud Flows.

For example, I wrote a cloud flow for a client that needs to run an annual process, but after a couple months, I got notified that it was deactivated. Now I have to write flows that run on a schedule to keep the other flows active.

Another example, I have a client using Field Service Inspections, and there is an OOTB Cloud Flow "Deserialization of Inspection Response". In the Sandbox, there has been no need to run that flow, so (I believe) MS turned it (and all child flows) off. Then when the client needs to run that flow to test an update, they get an error message "<name of flow> flow must be in published state".

When I try to turn it on the Cloud flow, I cannot turn on the flow because it has child flows (referred to only by a GUID in the error message) that also need to be published. I edited the parent flow and cannot find any reference to a child flow. And because all the OOTB MS flows are in Managed solutions, I cannot export them to find the GUID of the child flow.

Quick Links

Leaderboard