How long does it take PowerAutomate to catch up with SQL changes?

[stapes]

The Flow builder cannot see my Stored Procedure. It clearly exists!

It is giving me this message:

The dynamic operation request to API 'sql' operation 'GetProcedure_V2' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: { "status": 400, "message": "The key didn't match any rows in the table. inner exception: The key didn't match any rows in the table. clientRequestId: ba4505cd-ff0f-4421-ba17-c02330247171", "error": { "message": "The key didn't match any rows in the table. inner exception: The key didn't match any rows in the table." }, "source": "sql-ukw.logic-ase-ukwest.p.azurewebsites.net" }

Why is it looking in  sql-ukw.logic-ase-ukwest.p.azurewebsites.net for it?

How long does it take to catch up. I have rebooted my PC twice, cleared all cached images in my browser twice. Deleted the flow and started again twice.

[manuelstgomes]

Hi @stapes 

The error is not that it can't find the stored procedure. The issue is with the parameters. It runs because it's returning "The key didn't match any rows in the table." so there's a problem in the input parameters that are being provided to the stored procedure.

Can you show the header of the stored procedure and the action that calls it so that I can try to understand whats wrong?

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

[stapes]

@manuelstgomes 

Sorry, I am afraid you are way off the mark. This procedure has no input parameters.

[manuelstgomes]

HI @stapes 

I'm interpreting the exception "This may indicate invalid input parameters.".

As I asked if you provide more information I can try to help you. With the information provided so far, I'm trying to guess what could be the stored procedure, what could be the action, etc. I need more information to help you. Indicating that there's no parameters is something that could help for example.

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

[stapes]

@manuelstgomes 

If it was peculiar to one stored procedure, I might agree with you, but it is happening to many of them.

[manuelstgomes]

Hi @stapes 

Wish you good luck but with no information I won't be able to help you..

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

[stapes]

@manuelstgomes 

This is the problem. It is not finding my Stored Procedure at all. It is not in the drop down list (shown).

When I type the procedure name in 'Enter Custom Value' is when this message appears.

[stapes]

@manuelstgomes 

Whilst we have been talking, it has finally caught up, & the problem has solved itself. My question still stands.

How long does it take PowerAutomate to catch up with SQL changes, & why?

Until we get a clear answer to this the problem will keep arising.

[msmirnov]

@manuelstgomes 

Same problem here. SQL component in the Flow take a long time to start seeing new stored procedures. Sometimes takes 30 minutes for the list to refresh.

[mecartistronico]

Similar problem here?

This Flow ran many times successfully, as is, and then suddenly it started failing. As above, the Stored Procedure takes no parameters. 

[ABDataGuy777]

I have the same issue. Stored procedures that were running fine are failing. I believe it is because I changed database permissions on the account running them from db_owner to db_writer. I advise to check the db permissions for the connection running the flow. It worked for me