Dynamics Community Forum Thread Details

Hello grant_barth,

You've encountered a rather specific error message ("The rule is disconnected from the Power Automate flow") for Dynamics 365 Customer Service Automatic Record Creation (ARC) rules. The fact that a Google search yielded no results suggests this might be a less common or recently introduced issue.

Here's a breakdown of potential root causes and areas to investigate:

Understanding the Integration:

ARC rules in Dynamics 365 can be configured to trigger Power Automate flows for more complex actions beyond the standard record creation. This integration relies on a connection or reference between the ARC rule and the specific flow. The error message clearly indicates that this link has been broken.

Possible Root Causes:

Environment Instability or Transient Issues:
- There might have been a temporary glitch or instability within the Dynamics 365 or Power Platform environment that caused the connection between the ARC rule and the flow to drop. These transient issues can sometimes resolve themselves with a reactivation.

Power Automate Flow Modifications (Without Updating the ARC Rule):
- Flow Deleted and Recreated: If the Power Automate flow that the ARC rule was linked to was deleted and then recreated (even with the same logic), the internal ID of the flow would have changed. The ARC rule would still be pointing to the old (non-existent) flow.
- Flow Environment Change: If the flow was moved to a different Power Platform environment, the connection from the ARC rule would be broken.
- Significant Flow Modifications: While less likely to directly cause a "disconnected" error, substantial changes to the flow's triggers or connections might, in some internal processes, lead to a broken link with the ARC rule.

Dynamics 365 Updates or Patches:
- It's possible that a recent Dynamics 365 update or patch had an unintended side effect that disrupted the connection between ARC rules and Power Automate flows in specific scenarios.

User Permission Changes:
- If the user account that initially configured the ARC rule or the Power Automate flow had their permissions significantly changed, it could potentially impact the connection, although this is less likely to result in this specific error message.

Connector Issues in Power Automate:
- Temporary issues with the Dynamics 365 connector within Power Automate could have caused the link to become unstable.

Internal System Processes:
- There might be internal background processes within Dynamics 365 or Power Platform that manage these connections, and a failure in one of these processes could have led to the disconnection.

Troubleshooting Steps:

Review Audit Logs:
- Check the audit logs in both Dynamics 365 and Power Automate for any events that occurred around the time the ARC rule stopped working. Look for errors, modifications, or deletions related to the ARC rule or the associated flow.

Examine the ARC Rule Configuration:
- Open the affected ARC rule and carefully review its settings, especially the section where the Power Automate flow is linked. Ensure the correct flow is still selected.

Inspect the Power Automate Flow:
- Open the Power Automate flow that was linked to the ARC rule. Check its run history for any failures or errors around the time the issue occurred.
- Verify that the flow is still active and that its connections are valid.
Check Solution Layers (If Applicable):
- If the ARC rule or the Power Automate flow are part of a managed or unmanaged solution, review the solution layers to see if any other customizations might be interfering.

Monitor for Recurrence:
- Keep a close eye on this ARC rule and any other ARC rules that utilize Power Automate flows to see if this disconnection issue recurs. If it happens again, it could indicate a more systemic problem.

Consider the Timing:
- Was there any specific action or event that preceded the ARC rule stopping working (e.g., a Dynamics 365 update, a change to the Power Automate flow, a user action)?

Contact Microsoft Support:
- Given the lack of information about this specific error message online, it would be prudent to raise a support ticket with Microsoft. Provide them with the error message, the steps you took to resolve it, and details about your Dynamics 365 and Power Platform environments. They might have internal knowledge of this issue or be able to identify underlying problems.

Preventative Measures:

Avoid Deleting and Recreating Flows: If you need to make significant changes to a flow linked to an ARC rule, try to modify the existing flow instead of deleting and recreating it. If recreation is necessary, ensure you update the ARC rule to link to the new flow.

Careful Environment Management: Be mindful of moving flows between environments, as this will break the connection with the ARC rule.

Monitor Flow Health: Regularly check the health and run history of your Power Automate flows.

Document Integrations: Maintain clear documentation of which ARC rules are linked to which Power Automate flows.

While the exact root cause in your client's case remains unclear, by systematically investigating the potential areas outlined above, you might be able to shed more light on why the disconnection occurred. If the issue persists or you need further assistance, reaching out to Microsoft Support is the best next step.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

ARC rule disconnected from Flow

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

Featured topics

Product updates