The caller with object id does not have permission for connection under Api 'shared_sql' and failed during http send request errors

[knives]

I am creating a simple flow using a service account that has all the correct permissions for both power automate and powerapps and all the relevant data sources.

I cannot test this flow in power automate and I cannot add the flow to powerapps. My manager is the only person who can test the flow and add the flow to powerapps.

I cannot understand why this is happening as I have had several other view similar flows that are using the service account > data source connection with no issues and have been able to add these to my powerapp with no problems. I understand that this is a permissions issue but I cannot understand where the issue is stemming from as it was working on Monday and suddenly stopped working yesterday. I was hoping that the issue would resove itself if left overnight as many other users have experienced but this doesn't seem to be the case.

I've gotten very far in creating this app and all the flows associated so re-creating this app and all flows is not an option.

Any help would be much appreciated

[so96ie]

I have the same issue too, 

All action under SQL Server option always fails. The 'Server Name', 'Database Name', and 'Table Name' input fields always show error 'Could not retrieve values. The caller with object id { objectid } does not have permission for connection { connectionid } under API "shared_sql"'.

I have been using power automate since June 2019, and never experienced this before. 

Please fix this error. 

Thanks

[knives · Accepted solution]

For anyone experiencing the same issue this is what we did to fix the issue.

We restarted the gateway which fixed the majority of the connection issues on their own. For those that did not fix with a restart, we went into the connections section:

Unshared with everyone, including those who have edit permissions, so that only the owner is left and re-shared. Then went back in and re-added people with the correct permissions.

[AnotherRedbeard]

I was having a very similar issue to this inside of a flow that was trying to use a SQL Server Connection, but it wasn't able to find the server and database all of a sudden.  Our problem was fixed by editing the connection and reconnecting to the database.  This can only be done by the owner of the connection.

Hope that helps someone!

[HelpfulBit]

Hi,

It appears you've figured it out, but I've seen this a few times, with different connectors and decided to share what I've found is a common cause for flow connection references not working. https://helpfulbit.com/connection-references-caller-does-not-have-permission-for-connection/

If you find this keeps happening, the article migh shed some light on why.

This older article may also be helpful https://helpfulbit.com/upgrade-flows-to-use-connection-references/ 

Feel free to reach out with any questions.

Ryan.

[Therese1]

I got this same error while trying to Export a Canvas PowerApp.  The issue turned out to be a Flow/Power Automate that no longer existed was referred in the Canvas App.  Deleting the extra Flow fixed my issue. Hope this helps someone. 

[Khuys]

A good afternoon,

I had to update my gateway software, and I can't update my connections, I get the following errors 'The Caller with the object Id does not have the minimum required permission to perform the requested operation on connection under API 'shared_sql'

When i use the account directly on sql server I have to problems to login with that account, 

but when I want to make the connection then it doesn't work, I had a look on the web, but at this moment nothing helps me to resolve the problem, 

-the Gateways is active (no errors there)

- tried to adjust a connection that I had that I want to update : does not worked

- tried to make a new connection same error, 

is there somebody that have a sudjestion, 

I am working with sql 2008 and logging in with windows Authentication (that worked till yesterday like it should

Koen

[HelpfulBit]

HI @Khuys , Did you read the post I linked above, back in 2021.  It has been a while, but if I recall the specifics correctly, this happens when the flow references a connection that the calling user can't access / use.  But, simply creating a new connection doesn't always fix it as the connection privileges appear to be evaluated when the flow is activated, so you may need to deactivate and reactivate, even if you've updated the connection.  TRY deactivating the flow, remove the old connection, save the flow. Create a new connection, which you own, add to the flow, save and reactivate to ensure the flow isn't using a cached reference to the old connection.   

I'll also note - you didn't mention solution deployments, but, when I did that write up, I noted that the solution deployment process didn't always trigger such connection references to refresh if the underlying connections aren't accessible to a different account than what was originally used to deploy an updated version of the flow / connections. The deployment would break it requiring you 1) verify the connection was in facti shared with the user, and 2) re-enable the flow to ensure the flow permissions were re-evlauated to reflect this. Of course, it has been nearly 2 years and MSFT may have identified and fixed this aspect since then. 

I don't fully follow the steps you've taken, but hopefully this helps.  If not, perhaps we can hop on a call some time if you haven't otherwise figured it out. 

Ryan.

[Khuys]

I did everything as the above, but I am still not able to connect

[flowForm]

Hi all

I face a similar issue with the error "The caller with object id '9a13e5dc-2563-4034-bb27-1a4c00f5a53f' does not have the minimum required permission to perform the requested operation on connection '99db8037c5c64daeae3b916e11a1a248' under API 'shared_powerappsnotification'."

Things I have tried -

1. Remove all connections and re-shared

2. Turning off power automate flow (to send notifications) and turning it on 

3. Did above steps and tried to publish, but still failed.

4. I have no power apps admin access, unable to remove connections.

Does anyone have any idea how to go about to solve it?

[Khuys]

A good morning, my problem got solved yesterday

- I downloaded the gateway again from the website

- I turned off the flows

- I normally log in with windows authentication, I changed it to sql authentication

- server name: instead of using the server name, I used the ipnumber 

the connection whent through, then I turned on the flows again, and in the app I had update the connections

Kindest regards

[InfinityAlarm]

In case anyone else runs into this and does not find success with any of the suggested solutions, I'll add a little context of my situation and what worked for me in case it helps.

I'm kinda a bit of a noob to the Power Platform 😅 and had built a decently complex app using Power Apps and Power Automate. I had a SQL Server Connection that both used (Power Apps used it to read in some data for the app, Power Automate used it to insert or update data to the same database), however being the noob I am, I'd been working on this all with my domain credentials. When my password changed, it broke everything. I got a service account set up to use for authentication, and had to re-create the Connection. I updated the Data Source in Power Apps, and got Power Automate to recognize the re-created data source, but when I couldn't publish the app because I kept getting the

The caller with object id [hex id string] does not have the minimum required permission to perform the requested operation on connection [hex id string] under API 'shared_sql'.

message. I tried everything listed here, plus recreating the connection yet again to no avail. What finally worked for me was deleting all the flows from the Power Automate tab in Power Apps, publishing, adding them back, then publishing again. I feel kinda dumb for not trying that sooner, but hopefully that helps someone! 💖

[shred_yerbootie]

Had the same issue, which led me to this page. Turned out to be an issue with the PowerAppsNotificationV2 connector (see image). Once I deleted that, I was able to publish my app, and all was suddenly well with the world. 

Hope this helps someone ... have a great day! 

[shred_yerbootie]

Hi again -- apparently I can insert an image in my post. Woooo!!  😁

This is the connector I alluded to in the post above (so now you don't have to download anything...) 

To recap: this is how I resolved the issue which led me to this page: I deleted the PowerAppsNotificationV2 connector, and then I was able to publish my app. Anyone listening at MSFT?  🙄

[bwbrandiwoodson]

So I was building a manually start trigger flow. I was receiving this same error when testing from another account. I don't understand why but the only way I got it to work is when I added the user attempting to request approval as a co-owner of the flow which is NOT what we'd want to do.

Was there any resolution to this? How do we allow users to trigger the flow (flow owner) and let the workflow run under the credentials for all the other actions in the flow without requiring to add all users as a co-owner?