Skip to main content

Applies to Event Management & Employee Training Management

Troubleshooting Power Automate Flows

Our SharePoint-based Event Management and Employee Training Management applications can be extended using Microsoft Power Automate. Many customers enhance their processes with flows such as:

  • Approval workflows

  • Reminder and notification emails

  • Scheduled data processing

  • Data imports and synchronization

  • Custom business logic

We provide a range of flow templates to help you get started, and we also offer premium support for designing and building advanced, customized flows. However, once flows are deployed in your environment, the customer is responsible for maintaining and troubleshooting them. This guide explains how to diagnose issues, identify failing actions, and collect evidence for support.

1. Understanding How Power Automate Executes Flows

Before troubleshooting, it’s important to understand how Power Automate runs flows:

  • Flows are triggered by SharePoint, schedules, or connectors.

  • Each run has a detailed Run History.

  • Each action shows inputs, outputs, and execution details.

  • Permissions, connectors, and data changes can affect flow behavior.

2. First Steps When a Flow Stops Working

2.1 Check Flow Run History

  1. Open the flow in Power Automate.

  2. Select Run history.

  3. Look for failed or cancelled runs.

  4. Open a run to view the failing step.

2.2 Confirm the Trigger Behavior

Common trigger issues include:

  • SharePoint item changes not firing

  • Incorrect trigger conditions

  • Connector authentication failures

  • Changes in underlying data structure

2.3 Check for Disabled or Quarantined Flows

Flows may be disabled automatically due to failures, expired connections, or licensing issues.

3. Troubleshooting Common Issues

3.1 Connection Problems

Typical symptoms include invalid connections or instant failures.

Fix: Reauthenticate connectors under Data → Connections.

3.2 Permission or Access Denied Errors

Flows often fail when the creator loses permissions or leaves the organization.

Fix: Use a dedicated service account; ensure correct list/library permissions.

3.3 SharePoint Structure Changes

Flows can fail when fields are renamed, deleted, or modified.

Fix: Edit affected actions and reselect the correct fields.

3.4 Logic or Condition Failures

Conditions may prevent actions from executing even when the flow runs successfully.

3.5 Email or Notification Issues

Verify email recipients, shared mailbox permissions, and Outlook connector authentication.

4. How to Identify the Failing Action in a Flow Run

When a flow fails, locating the exact failing action is crucial. Flows often contain nested structures like loops, scopes, and conditions, so the failing action may not be visible until everything is expanded.

4.1 Open the Run Details

  1. Go to the flow.

  2. Select Run history.

  3. Click the run marked Failed.

4.2 Expand All Nested Elements

Expand all:

  • Conditions

  • Apply to each loops

  • Switch cases

  • Scopes

  • Do Until loops

  • Parallel branches

This reveals the full execution path and ensures you can locate the failing action.

4.3 Locate the Action Marked as Failed

A red X indicates the failing action. If a container (such as a scope) is marked as failed, expand it to find the root cause.

4.4 Review Inputs and Outputs

Click the failing action to view:

  • Inputs – the data or parameters passed in

  • Outputs – error details, system messages, status codes

This is essential for determining the root cause.

4.5 Collect Evidence for Support

Please gather:

  • Screenshots of the failing action

  • Inputs and outputs

  • The Run ID

  • Recent changes to data, lists, or permissions

  • Optional: exported flow package

5. Preventing Future Flow Issues

  • Use a dedicated service account.

  • Document flows thoroughly.

  • Test flows after any SharePoint list changes.

  • Monitor run history regularly.

  • Keep flow logic simple where possible.

6. When to Contact Premium Support

Premium support can assist with:

  • Designing advanced flows

  • Troubleshooting complex issues

  • Flow architecture improvements

  • Integrations and data automation

Even with premium support, customers remain responsible for long-term flow maintenance. Our team assists with creating solutions, but ownership remains with the customer. If you are interested in a premium support packages, please contact us and we’ll send you a formal quote.

Tags:
In this article
SharePoint|sapiens