Error when repeatedly calling a custom connector

[jrestebanez]

I have created a custom connector to be able to obtain the latest executions of the different flows we have in the organisation following the indications of this blog

When I do the test it works correctly as well as when I invoke the custom connector from a cloud flow to query a particular flow.

We are using CoE Starter Kit (without BYODL) and there is a table called Flows (admin_flow) and this is where the problem comes in, as we currently have approximately 4000 flows in the different environments. The flow I'm doing, I want to report the last run date of each of the flows, so I have to loop through each of the flows and call the custom connector. The execution is correct until about 300 rows are processed and then the flow fails 😞 returning the following error:

The caller object id is 'xxxxx21-xxxx-4394-83f7-xxxxx556db'. Connection 'xxxxx961-xxxx-41d9-baa4-0004f79xxxx' to 'shared_logicflows' cannot be used to activate this flow, either because this is not a valid connection or because it is not a connection you have access permission for. Either replace the connection with a valid connection you can access or have the connection owner activate the flow, so the connection is shared with you in the context of this flow.

Could it be some throttling problem and that I close the connection? In the loop, I have set the Concurrency Control to 50, should I run it 1 at a time?

EDIT: I have made a new test, so that the loop is executed 1 by 1 and curiously when it processes 300 rows approximately, it fails again.

[jrestebanez]

I have finally found the problem, I hope this helps someone else and they are not as dumb as me.

When you make the API call to query the executions of a flow, if this is off, is when it gives the error, so to avoid this error

I have also been able to verify that there are other flows that, when making the call, fail depending on the connection references being used, so it seems that the main user or service with which the connection has been established must have sufficient permissions so that it does not fail.

Error despite running with Power Platform Administrator User

{
  "error": {
    "code": "InsufficientFlowPermissions",
    "message": "User does not have sufficient permissions for flow 'xxxxxxxxxxx'"
  }
}

Now I understand why the CoE Starter Kit team, the people who use the Cloud Flows version, have not reported the last execution date of the flows, to avoid these problems that I have encountered.