logo
search
Others

How to Troubleshoot Power Automate Create Item Branching Errors

John WilsonJohn Wilson Oct 1, 2026 868 views

Question details

The user needs to resolve an issue where a Power Automate flow skips a SharePoint Create item action and throws an ActionBranchingConditionNotSatisfied error.

How to Troubleshoot Power Automate Create Item Branching Errors
Product
Power Automate
Device & OS
not provided
Scenario
Running a Power Automate flow that uses conditional branching to create an item in a SharePoint list.
Observed behavior
The flow skips the Create item action entirely and returns the ActionBranchingConditionNotSatisfied error message.
Before you start

Before editing your flow, run a test and open the flow run history to pinpoint exactly which condition branch caused the action to be skipped.

Solution 1Recommended

Inspect Flow Run History and Debug Conditions

Use the built-in run history and Compose actions to identify why the branching condition evaluated to false.

The ActionBranchingConditionNotSatisfied error simply means the prerequisite condition for your 'Create item' action evaluated to false, causing the flow to skip it. You need to inspect the live data passing through the condition.

1
Open flow run history

Navigate to your Power Automate flow details page and click on the most recent failed run under the '28-day run history' section.

2
Review condition inputs

Expand the condition block immediately preceding the 'Create item' action to view the exact inputs that were evaluated during the run.

3
Check execution branches

Review the 'If yes' and 'If no' branches to confirm which path the flow actually took based on the condition evaluation.

4
Add a Compose action for debugging

Edit the flow, add a 'Compose' action right before the condition, map your dynamic content to it, and re-run the test to clearly inspect the dynamic values.

Inspect Flow Run History and Debug Conditions
Free Microsoft Office alternative

Discover a Lightweight Office Suite for Your Daily Workflow

While Power Automate handles complex cloud triggers and SharePoint integrations, you might need a fast, reliable desktop suite for your daily document and spreadsheet tasks. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office, featuring a familiar interface and seamless file management.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install the application: Run the downloaded setup file and follow the on-screen instructions to complete the installation.
  3. 3. Open and manage files: Launch WPS Office to easily create, edit, and save your documents, spreadsheets, and presentations.
Fully compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Lightweight installation that consumes minimal system resources.Built-in PDF editing, conversion, and annotation tools at no extra cost.Familiar, intuitive tabbed interface designed for seamless multitasking.
microsoft office alternative - wps office

Frequently Asked Questions

What does the ActionBranchingConditionNotSatisfied error mean in Power Automate?

This error indicates that an action was skipped because the prerequisite condition required to execute that branch evaluated to false during the flow run.

How do I check the exact values my flow condition is evaluating?

You can insert a 'Compose' action immediately before your condition step. Map your dynamic variables to this Compose action, run a test, and inspect the exact data outputs in the flow run history.

Why does SharePoint reject the dates sent from my Power Automate flow?

SharePoint generally requires date and time values to be in the standardized ISO 8601 format. If your flow sends a localized or incorrectly formatted date string, SharePoint may reject it or cause preceding validation conditions to fail.