"Error from token exchange permission denied due to missing connection ACL" while using Approval

(0) Share

Report

Posted on by WiZey

3,023 Moderator

Hello,

I'm using a simple flow where I collect properties of an element from a SharePoint list, then submit an approval to an user.

The thing is I have several flows like that, but there is only one which ends up with this error and I can't put my finger on the issue.

I tried to create a new connection, I tried to re-create the whole connector to send a brand new approval, I even removed the dynamic content I was using to populate the approval. And my licence doesn't appear to be expired or anything. I tried sending the approval to me directly, but even this doesn't work.

Does anyone have an idea about this?

Categories:

Using connectors

I have the same question (0)

All responses (6)

Answers (1)

WiZey 3,023 Moderator on at

Like (0)

Report

Hold on... I just noticed my flow actually lost its connections (SharePoint, Approvals, etc.). I'll try to re-establish them.

Was this reply helpful? Yes No
Verified answer

WiZey 3,023 Moderator on at

Like (0)

Report

Well yes, that seemed to be the problem. The flow somehow lost its connections which explain why he couldn't "connect" when trying to send the approval.

I still can't understand why the connections would vanish like that and I don't even know where to begin looking at for this, but at least my flow is working now.

Was this reply helpful? Yes No
novice1508 12 on at

Like (2)

Report

it happened to me when I changed the flow trigger from Recurrence (every 10 mins, with setting to run Only one session at a time) to Manually triggering the flow.
I noticed an error when I tried to save the flow, since the original trigger was different.
solution:
I created a new flow and copied all the flow actions, except for the List Files in Folder action. For that one I created a new action.
Everything seems to work without a glitch

Was this reply helpful? Yes No
NikitaSharma 10 on at

Like (0)

Report

Same for me!

Was this reply helpful? Yes No
MathewVaughan 2 on at

Like (0)

Report

I have had this error for days and tried to resolve it by updating the connection settings. In the end, I landed up setting up a new connection from the Flow in question and works fine now.

Was this reply helpful? Yes No
Belin on at

Like (0)

Report

It seems that the issue happens only when a flow is created with PowerBI and then edited with Power automate web.
This is the only time experienced, so I guess the solution is to keep edit the flow within PowerBI desktop (not sure the web version)

Was this reply helpful? Yes No