web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Critical: Condition an...
Power Automate
Suggested Answer

Critical: Condition and Switch actions fail with ‘has no inputs’ after designer update

(2) ShareShare
ReportReport
Posted on by 4

Multiple flows are failing after a recent designer update.

Conditions and Switch actions show as configured but at runtime fail with “has no inputs”.

Symptoms:


  • Compose actions clearly output correct values (e.g. Forms choice = “New” / “Update”)
  • Condition and Switch actions referencing those outputs fail immediately
  • “Edit in advanced mode” is no longer available
  • “Peek code” is greyed out
  • Rebuilding the control actions does not resolve the issue
  • Multiple flows are failing after a recent designer update.
  • The issue persists even when values are confirmed via Compose and affects both Condition and Switch control action
  • Rebuilding the Flow from scratch does not resolve the issue
  • This appears to be a designer/schema regression, not a data issue, and is blocking production workflows.



  •  
I have the same question (0)
  • Suggested answer
    11manish Profile Picture
    1,537 on at
    This appears to be a Power Automate designer regression where Condition and Switch actions lose their input bindings at runtime, despite appearing correctly configured in the UI. The issue persists across rebuilt flows and is not data-related. Temporary mitigation includes using variables or manual expressions.
  • Suggested answer
    rezarizvii Profile Picture
    333 on at
    Hi, hope you're doing well.

    This does sound like a designer/runtime mismatch rather than anything wrong with your logic.
     
    A couple of things that have worked in this situation:
    • Open the flow in classic designer (if you still have the option via URL tweak) and check if the actions render properly there
    • Export the flow as a package and re-import it. This sometimes forces the schema to rebuild cleanly
    • As a quick test, recreate just the failing Condition/Switch in a different branch (not inline replacement)
     
    If this reply helped you in any way, please give it a Like 💜 and in case it resolved your issue, please mark it as the Verified Answer ✅.
  • André Arnaud de Calavon Profile Picture
    545 on at
    Hi Illya,
     
    Are the flows working correctly in case you switch back to the classic designer? Can you share details how to reproduce this issue? 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 516

#2
Valantis Profile Picture

Valantis 477

#3
Vish WR Profile Picture

Vish WR 470

Last 30 days Overall leaderboard