Error: The usage configuration '' could not be found in integration account

(0) Share

Report

Posted on by CU12080107-1

I keep getting the same error "Error: The usage configuration '<null>' could not be found in integration account" when I try to run a flow. It was working fine a few weeks ago and I haven't changed anything, it just started doing this and I haven't been able to fix it. Other accounts that use the same flow are not having any problems running it. Any advice would be appreciated.

Categories:

Using flows

I have the same question (57)

All responses (11)

Answers (0)

stampcoin 5,072 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@CU12080107-1 Hi,

Since you didn't change the flow, could it be something wrong with the account ?

Double check the account, delete the connection reference, and recreate the connection for that account.

1 people found this reply helpful.

Was this reply helpful? Yes No
AA-19081303-0 2 on at

Like (0)

Report
Copy link

Link copied!

I too am having this same error for 1 specific user. I have confirmed that about 20 other users are able to use the flow successfully so that rules out issues with any connections. And have checked working users' MS365 group memberships against the non-working user's and can see no differences that might account for it. I have removed the user's power automate licence and re-added. After the error message in my case is a GUID which is the same each time the error occurs, but I can't match this to either a user, connection or flow, and isn't the meta id of any of the elements of my flow. I know this isn't telling you the fix for this but I just wanted to clarify for anyone else with the same issue, things that it probably isn't caused by, maybe it might help?

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

AS-11091554-0 2 on at

Like (0)

Report
Copy link

Link copied!

I started getting the same error message for some users when a flow was called from a power app. Uninstalling Power Apps from the user's device and re-installing it fixed the issue for me.

1 people found this reply helpful.

Was this reply helpful? Yes No
CU05021234-0 2 on at

Like (0)

Report
Copy link

Link copied!

I am have the same issue and tried several possible solutions
Unfortunatly, did not find a solution.
If anyone has found a working solution, please share it.

Was this reply helpful? Yes No
lukap07 10 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I have the same problem. Some of the users started to get this error a few days ago, but it was working for them previously. I can't find a solution to this. It is definitely not the problem with flows or connection, because most of the users can normally use the flow.

My use case is Sharepoint list that has a button to run the flow and it was working for more than a year now without any problems.

I also tried to clear the cookies and cache on user's devices, tried Edge and Chrome browser, tried Incognito mode but nothing worked. Additionally I added the users as Run-only users directly (normally users get Run-only permission via Sharepoint list) but that did not help as well.

Did anyone find the solution for this?

Was this reply helpful? Yes No
SS-30071228-0 2 on at

Like (0)

Report
Copy link

Link copied!

I've also had this problem reported this morning. Our use case is the SharePoint page publishing approval workflow - which calls a Power Automate flow. It works for me, but 3 other users have reported this error this morning. I'm going to raise a ticket with Microsoft 365 Support. Nothing has changed at our end, and all the connection references in Power Platform appear to be fine.

Was this reply helpful? Yes No
lukap07 10 on at

Like (0)

Report
Copy link

Link copied!

@SS-30071228-0 if you find a solution or get any useful response from Microsoft support, please post it here. I am still stuck with this problem and can't find a solution for the problem.

Was this reply helpful? Yes No
SS-30071228-0 2 on at

Like (0)

Report
Copy link

Link copied!

We thought yesterday the problem was fixed - because the page publication approval flows started working again (for all users). However, I've had a report this morning from a user who says it's not working, but they've now gone "out of office", so I can't explore further with them yet.

So far, I raised a ticket in the Microsoft 365 Support Center, but was then told they wouldn't accept it, because it was a Power Platform issue. I had to then get access to the Power Platform Admin Center on our tenant so I could report it there. Then, the Power Platform guys said it wasn't their area, so they've pushed it back to the Microsoft 365 Support people. Typical Microsoft. When (or if) I get a resolution, I'll update.

Was this reply helpful? Yes No
Der Galven on at

Like (0)

Report
Copy link

Link copied!

Having the same issue. Only affects a single user, and nothing changed at our end.

Was this reply helpful? Yes No
Suggested answer

CU12021247-0 on at

Like (0)

Report
Copy link

Link copied!

Good day,

We were experiencing the same issue, everything looked fine in the flow and the connections, but when we changed the user that was experiencing the issue from a "member" to an "owner" on the SharePoint site, this resolved the problem and the user can now run the flow without the error coming up.

We have not tested changing the user back to a member yet to see if the error reappears but will update this post once we have tested some more.

So we went to the members link on the site and changed the user's permissions from member to owner.

Update: The user was changed from an "owner" back to a "member" and they were able to start a new flow again.

Seems as if it was permissions related but why it changed in the first place, we do not know.

Was this reply helpful? Yes No