{Stored Procedure} failed: The request was not sent or there was no response from the server.

(1) Share

Report

Posted on by CU12090902-0

Hi,

We are working on Canvas App & performing CRUD operations using Azure SQL Server Database using only Stored Procedures via data gateway.

The SQL Server connector uses the data gateway to connect to the Azure SQL Server Database. I am also able to connect to the Azure SQL Server Database using SSMS.

We are making direct Stored Procedure calls using SQL Server connector via Canvas App (https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/connections/connection-azure-sqldatabase)

The Stored Procedure calls using Canvas App works majority of the time via data gateway.

We are calling Stored Procedure in Canvas App on click of button (OnSelect event) & triggering this button click event on load of screen in some cases.

Sometimes, when the screen is loading, we randomly get errors like "{Stored Procedure} failed: The request was not sent or there was no response from the server. Please check your internet connection."

Please provide solution for the above error.

Thanks in advance.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Michael E. Gernaey 53,362 Super User 2025 Season 2 on at

Like (0)

Report

when you say the screen is loading do you mean code in the appOnstart or code in the Onvisible?

If its the appOnstart, 1) make sure asynx for App Onstart is set

2) move it to the OnVisible of the screen instead

Was this reply helpful? Yes No
CU12090902-0 4 on at

Like (0)

Report

We are calling Stored Procedure in Canvas App on click of button (OnSelect event) & triggering this button click event on load of screen in some cases.

Was this reply helpful? Yes No
timl 36,391 Super User 2025 Season 2 on at

Like (0)

Report
I've seen cases in SQL Azure where the "auto-pause" feature has paused the database. The request that wakes it can take a minute, and this is a potential cause of the 'no response from the server' error.

To prevent this, you could try capturing the error within a call to IfError and try calling the stored procedure again.

IfError(CallStoredProcedure..., CallStoredProcedure )

Was this reply helpful? Yes No