Unanswered

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

(0) Share

Report

Posted on by VR-29070522-0

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

I have the same question (0)

All responses (3)

Answers (0)

JZ-14021528-0 2 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
TN-08072251-0 2 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
SJacobs 71 on at

Like (0)

Report

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)".

Was this reply helpful? Yes No