Unanswered

caller does not have permission for connection under Api 'shared_logicflows'

(0) Share

Report

Posted on by Bjorn

Can anybody shed some light onto this error?

The caller with object id 'bb7e6e0a-5b3c-4ed7-84b3-ce5bfd766136' does not have permission for connection '1ca80354-17fc-48e6-a653-01b5f9179f1b' under Api 'shared_logicflows'.

It randomly appears on one Flow of mine and I have no idea what it's even referring to. Is the first GUID for a specific run or user? Is the second GUID for a specific connection? I looked at my connections but don't see that GUID anywhere in the details. The urls have strings like connectionName=ca92c83e87654ee18e0c6c50452dfc5d but they don't match the error message.

Categories:

General topics

All responses (4)

Answers (0)

Sort by

AlanPs1 2,471 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Bjorn , thank you for your post!

some additional info here: https://powerusers.microsoft.com/t5/Using-Flows/Invalid-Connection-error-on-a-Flow-that-has-been-working-fine/m-p/77910

It looks to be permission or connection related and the user experiencing it here says it resolved after a couple of hours. Maybe you could recreate your connections to your connectors and see if it helps.

If you have found my post helpful, please mark thumbs up.

Any other questions, just ask.

Thanks, Alan
Bjorn 92 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks Alan. I shared the Flow with a service account I use and I haven't seen the error since. That doesn't make any sense to me though, given that connection credentials and Flow ownership are two different things. I really wish MS would provide some guidance on what the GUIDs in these error messages realte to.
Paperclip77 2 on at

Like
a
(0)

Report
Copy link

Link copied!

We are hitting this error, and I can say that the first GUID is the user's GUID. we checked in the Users table in CDS. I assume, then that the second GUID is the connector.

I find it very strange that existing flows keep working, and only new flows are having this issue (that's our experience at this time, anyway)
RyanCPerry 32 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Bjorn, @Paperclip77 . This may be a little late, but I've run into this with my own team and decided to do a write up about how to fix the broken connection references. https://helpfulbit.com/connection-references-caller-does-not-have-permission-for-connection/

It appears your flow is using connections, not connection references, so you may also want to look at an older post https://helpfulbit.com/upgrade-flows-to-use-connection-references/ as well. Let me know if you are still running into issues.
Hope this helps.

Ryan.