Unanswered

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

(0) Share

Report

Posted on by AR-10111507-0

Hello,

One of my colleagues is experiencing this error when trying to run a Power Automate flow from Power Apps and Power Automate. The user can view the flow, edit and save the flow, view the run history but cannot kickoff or test the flow. However, I have full access to run and test the flow.

"The usage configuration '<null>' could not be found in integration account '[GUID]'"

It is frustrating because we did not move the flow or change any of the connection references and this is effecting an urgent deliverable. All connections are operational, too. I saw a few instances of this error in the forums without any promising fixes.

Can anyone help fix this error?

Categories:

Error handling

I have the same question (4)

All responses (5)

Answers (1)

developerAJ 4,628 on at

Like (0)

Report

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

manually share the connections with the user and if flow got premium connectors make sure user got access

i would try debugging using developer tools from the browser to figure out exact error

Was this reply helpful? Yes No
Manc_Gurl 41 on at

Like (0)

Report

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

@AR-10111507-0 I started experiencing the same issue yesterday with some of my flows that are shared with other people. This appears to be affecting some, not all users. Some of the affected users are co-owners of the flows and some are run only users, they are all getting the same error message as the one you shared above.

If this was a connection issue surely it would affect all of the users with access to the flow, not just some of them?

1 people found this reply helpful.

Was this reply helpful? Yes No
AR-10111507-0 6 on at

Like (0)

Report

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

I am not sure how to manually share connections. I get this error when I attempt to do that for any of the connections. The user is a co-owner of the flow and is able to edit and save it but can't run it.

Was this reply helpful? Yes No
Verified answer

Manc_Gurl 41 on at

Like (0)

Report

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

@AR-10111507-0 I was able to get the flows working again for the affected users, although the resolution is very odd and I still don't understand the cause of the issue. This issue was affecting some run only users and some co-owners. Note that not all users of the same flow were affected, some users could still run the flows without issues.

All of the flows in this case use the same connection reference, so I tried changing the connection (new connection) being used by that connection reference and waited for the flows to update. This made no difference and the users were still getting the same error. I also advised the users to clear the browser cache for all time, this also had no effect.

In the end I went into one of the affected flows that a user could not run (the user could not run multiple flows) and I created a new connection reference for SharePoint and new connection. I then changed the connection reference being used for every SharePoint action in the flow and saved the flow. The user confirmed they could now run that particular flow. The interesting part is this, they also could run all of the other flows that they could not run previously, even though I had not changed their connection references and they were still using the old connection ref.

So I have no idea what is causing this issue all I know is that the above seemed to work for me.

1 people found this reply helpful.

Was this reply helpful? Yes No
AR-10111507-0 6 on at

Like (0)

Report

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

@Manc_Gurl that worked! I created new connection references for all connections and my colleague can run it again.

Again, there was no indication in the errors message that this was related to connections and there were no changes in flow configuration. It is frustrating how useless the messages can be in instances like this.

Was this reply helpful? Yes No