Actions have plug symbol- request failed with status code 500

(2) Share

Report

Posted on by danru

Hi,

I built a flow with a variety of actions and it was working fine before.

I opened it today and see some of the actions in my flow have broken.

This should be an excel connector but it's presenting like this.

I checked my connections (all are connected and fine). can't pin point what caused this.

I appreciate any help and suggestions.

Thanks so much.

Regards,

Daniel

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (0)

HaseebF 11 on at

Like (1)

Report

Running into the same issue. Happened to a 'Get Profile' action and a 'Get Items' from SharePoint action.

Was this reply helpful? Yes No
LindseyT 20 on at

Like (0)

Report

Having the same issue with the Get Items SharePoint connector. Anyone have any ideas? I was leaning toward an issue with the SharePoint list having too many items on it, since it just went over 5,000. But seeing that its also happening on an excel connector makes me think that isn't correct.

Was this reply helpful? Yes No
HaseebF 11 on at

Like (1)

Report

I deleted and recreated the action and seems to be working. Obviously that is a bit of a headache as you have to replace all dynamic content etc. that comes from that action.

Was this reply helpful? Yes No
danru 95 on at

Like (0)

Report

Hi Everyone,

So some feedback. I managed to overcome this. My flow is in a solution so on the flow (in the solution) I clicked on the three dots>advanced>Add required objects.

When I went into the flow again the errors had cleared.

However, I did go out of the flow and in again a few times and each time it was happening with different connectors- Ones that were fine before were now exhibiting this error and ones that had the error were fine on subsequent tries and it keep changing as I exited the flow and edited again.

I didn't delete any actions or touch anything.

I only tried the 'add required objects' after this and it seems to have done the job.

A number of the connection references, etc seem to have vanished somehow so this action seems to have put back what went missing.

How it happened is anyones guess.

Maybe it's a service health issue.

Thanks everyone for your help and input.

Hope this helps.

Regards,
Daniel

Was this reply helpful? Yes No
LindseyT 20 on at

Like (0)

Report

Appreciate the update. Interesting to hear, as we have been seeing a fair amount of seemingly random issues with connections references across different solutions/environments. Thanks again!

Was this reply helpful? Yes No