Skip to main content

Notifications

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate - General Discussion / Bug in Execute Stored ...
Power Automate - General Discussion
Unanswered

Bug in Execute Stored Procedure (V2): Parameter Mappings Reset After Save

(0) ShareShare
ReportReport
Posted on by VR-29070522-0 4
The Execute Stored Procedure (V2) action in Power Automate allows users to call SQL stored procedures with specified parameters. However, a persistent bug has been observed where parameter mappings are reset, lost, or become empty after the flow is saved and reopened. This behavior causes significant disruptions, as the stored procedure may fail to execute correctly due to missing or incorrect parameter values.
Categories:
Process Advisor
  • JZ-14021528-0 Profile Picture
    JZ-14021528-0 2 on at
    Bug in Execute Stored Procedure (V2): Parameter Mappings Reset After Save
    I'm experiencing the same bug, with the same reproduction steps as mentioned by SJacobs. Unfortunately we are running through an on-prem gateway, so "Execute a SQL query (V2)" is off limits for us (which is another several-year-long issue that I'm amazed still hasn't been addressed). 
     
    To anyone else with this issue, what worked for me was switching back to the classic designer. It seems this bug only persists with the new designer. Switching back to classic, I've been able to save, close, re-open, edit other parts of the flow, etc. and keep my parameters in place. 
     
     
  • TN-08072251-0 Profile Picture
    TN-08072251-0 2 on at
    Bug in Execute Stored Procedure (V2): Parameter Mappings Reset After Save
    I have experience this issue as well.  In fact I ran across it again today.
  • SJacobs Profile Picture
    SJacobs 71 on at
    Bug in Execute Stored Procedure (V2): Parameter Mappings Reset After Save
    I am experiencing this same issue.  How to reproduce: (using new designer)
     
    1) Create a flow using Execute stored procedure (V2)
    2) Select a procedure that includes parameters.
    3) Set parameter value by using output from another action.
    4) Save flow. Exit flow design.
    5) Returning to flow, make edit to other actions (not the Execute stored procedure (V2) action)
    6) Save flow.
    7) Observe that the input parameters to the stored procedure are now empty.  When the flow is run, assuming the Stored Procedure requires parameters (ie they are not optional), the action will fail with error stating that the parameters were not supplied.
     
    My current work-around:  Replace use of " Execute stored procedure (V2)" with "Execute a SQL Query (V2)".
     
     

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

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 497 Super User 2025 Season 1

#2
David_MA Profile Picture

David_MA 436 Super User 2025 Season 1

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 244 Super User 2025 Season 1

Last month Overall leaderboard

Featured topics

How to Ask for Help with Your Power Automate Workflow

Product updates

Microsoft Power Platform Community release plans