There's a problem with the flow's trigger. Code: 502 Message: "Unable to connect to the remote server"

[Y_R]

Hello All,

I have been having random error messages popping up on some of my Flows with the following message:

First, I see this message about my "Runs" log

Then, when I click into the error, I get the following message

{

"error": {

"code": 502,

"message": "Unable to connect to the remote server",

"source": "flow-apim-msmanaged-na-northcentralus-01.azure-apim.net",

"path": "forward-request",

"clientRequestId": "1d017093-0124-41a0-9886-837152959c39"

}

}

Now, I've found a workaround to this, where I would add temporary Trigger, delete this erroneous one, then re-add it as the main trigger and delete the temporary one. The error goes away for a while until it randomly shows up again and I find myself having to repeat this method too often. It also prevents the Flow from kicking off.

Has this issue been happening with anyone else? Particularly with the error code and message combination (Code: 502 Message: "Unable to connect to the remote server")?

Please offer any thoughts as to why this may be continuously happening.

Thank you!

[showdwar]

I am having this exact same issue.  However, I didn't know about the work around.  

Any recommendation to OPs post is appreciated.

[yashag2255]

Hey @showdwar , @Y_R 

This type of an error was being observed in flows that were created from templates or as copies of another flow. A stable fix that was found is to export the flow as a zip package and import it back to the same environment, provide the connections while import and delete the previous flow. 

Can you try this and check if it resolves the issue? 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Y_R]

Hey @yashag2255 ,

Thank you for your reply.

I tried the method you suggested and the Flow imported successfully with no errors. However the real test is to observe how it behaves over time. I've never had an issue with exporting and importing flows, so I'm not entirely sure if this is the real solution. I can only tell after a lengthy period has passed.

Thank you for your suggestion. I will continue to observe the Flow to see if the error messages popped up again.

[yashag2255]

Hey @Y_R 

yep. You can observe the behavior for some time and check if it resolves the issue. 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[mpoppe]

Hi,

I'm having the same problem with some of my flows.  First time, I copied them and removed the original ones.  The problem was solved for a while, but it comes back after some time.  I'm not happy in having to copy or export/import a lot of my flows on a weekly basis. Is anyone aware of the cause of this problem, and how we can fix it permanently?

Regards,

Miriam

[Y_R]

Hello again @yashag2255 ,

I am back to report that this error message has popped up yet again. However this time, I am presented with a different error message:

{

"error": {

"code": 502,

"source": "flow-apim-msmanaged-na-northcentralus-01.azure-apim.net",

"clientRequestId": "b42a0b43-53cd-4b23-bdca-48444948f911",

"message": "The response is not in a JSON format.",

"innerError": "Object reference not set to an instance of an object."

}

}

I have not touched this flow in any way since I followed your method of exporting/importing it back into the same environment. It has just been working as usual until I got this message again.

Another thing is, I have been setting up and testing these Flows on a demo SharePoint page, which I intend to configure my production SharePoint page via a copy of this Flow in the future. But, with this issue currently being unresolved, I am not sure if I will get the same issue when choosing to copy Flows and reconfigure the URLs and/or use the exporting/importing it back into the same environment that was suggested. It's very worrying, because my Flows are fairly large and to have to redo them one by one from scratch is going to take up a lot of time. The last thing I thought would give problems were these features.....

Any updates as to why this may be recurring? Like everyone else who commented, I cannot keep going back to update this, since I am depending on Flow to do it's thing one I set it up... 

Thanks

[Y_R]

Hello again @yashag2255 ,

I am here to report that one of my other Flow is giving me this same error issue. There are different messages but i really don't know why because this particular Flow hasn't given me any issues before.

{

"error": {

"code": 502,

"message": "The remote name could not be resolved: '<mysite>.sharepoint.com'",

"source": "flow-apim-msmanaged-na-northcentralus-01.azure-apim.net",

"path": "forward-request",

"clientRequestId": "fcfb6e23-fada-4ab4-aa80-b544ef9f5159"

}

}

I'm really lost as to why this is occuring. i'm pretty anxious with the status of my Flows now...

[Y_R]

UPDATE

All of my Flows are now presenting me with the "There's a problem with the flow's trigger. Fix the trigger" error messages. 

Please help. ☹️

[lostgical]

Any update on this? It's starting to happen for us randomly too, most noticeable on large lists with over 20 or so columns. I find that using "Limit columns by view" will remove the trigger error for a while, so not sure if it has to do with load time on trigger for larger lists.

Looking for fix or other ideas to try please?

[Y_R]

Hey @lostgical ,

I can say that it still occurs on my end as well. I have not tried limiting the columns as you mentioned, but what I end up doing to avoid having to redo the entire flow is: make a copy of the flow with the error message and delete the previous version. For some reason, the copy does not contain the error.

The error message still occurs randomly just as you mentioned also, and I don't even know which Flow it affects until I actually go into the Flow itself or realize that some processes are not triggering via a particular Flow. I am not sure if there is going to be a fix for this soon, but I am really hoping there is...