Answered

Execute Stored Procedure V2 - Bad Gateway error but executing twice!?

(0) Share

Report

Posted on by TechServSup

I am really scratching my head on this one. I have a power app calling a power automate flow to run a simple stored procedure that enters new records in a table (it also used to work, but I am picking it up after about a year so I'm convinced something changed). I am receiving a timeout and bad gateway error in power automate (see below). What's amazing is when I go look in the database it does run, and seems to run twice as two records are inserted instead of one per transaction. So I don't understand why I get timeout or badgateway errors when it was able to run, and I certainly don't understand why it runs twice. When I run the stored procedure in SSMS it executes just fine (one record added). So I don't think there is anything wrong with the stored procedure itself. What is going on with the Execute Stored Procedure V2 action? Can anyone replicate? HELP!!

Categories:

Using flows

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

wskinnermctc 6,519 Moderator on at

Like (1)

Report

I have had issues with SQL Server connector whenever I make changes within the tables or even change my password.
The first thing I would try is recreating the stored procedure with a new name and everything (basically copy paste the stored procedure into new one with new name), then deleting the current flow step and replacing it with a new one to the new stored procedure.
If that doesn't work I would recreate the flow fresh, and/or go into my Data>Connections and deleting the current SQL Server connection and making a new one. Then delete and remake the SQL Server connection steps in the flow with the new connector.

Seems like a lot of work, but I know PA connectors to SQL Server doesn't always work seamlessly.

Was this reply helpful? Yes No
TechServSup 33 on at

Like (1)

Report

Thanks @wskinnermctc for the tips. I'll try that and report back.

Was this reply helpful? Yes No