Unanswered

Test connection failed. Details: Failed to fetch. Please see https://aka.ms/powerautomate-failedtofetch for more details. Send an email V2

(8) Share

Report

Posted on by ArsalanZoghi

Looks like there is sth wrong with Microsoft Connectors... getting this with multiple clients.. multiple tenants.. different flows and connections.

Some tenants even ask me to authenticate all my connectors... started happening only couple hours ago.

Anyone else having this issue? Already created a support ticket and waiting for them to contact me.

Categories:

Using connectors

I have the same question (0)

All responses (39)

Answers (0)

Sort by

Modulas 146 on at

Like (0)

Report
Copy link

Link copied!

I'm having this issue all of a sudden as well.

Was this reply helpful? Yes No
v-bofeng-msft Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi @ArsalanZoghi ,

This is a temporary issue and the product team is working on. I will monitor for updates , if there are any developments, I will provide an update in my response.

Best Regards,

Bof

Was this reply helpful? Yes No
alok_maheshwari 8 on at

Like (1)

Report
Copy link

Link copied!

I'm facing the same issue, looking for some resolution quickly to proceed with the work... I'm getting the same error when connecting to sql server using either my credentials or SPN credentials... both identities otherwise have required access on the sql server, however this issue to me looks like more of Azure AD related, as I'm unable to sign-in while setting up the connection using my credentials.

Was this reply helpful? Yes No
sunilss 4 on at

Like (0)

Report
Copy link

Link copied!

We are also facing the same issue, although its working for SharePoint Online connector. For other connectors its giving following error message. "Test connection failed. Details: Failed to fetch. Please see https://aka.ms/powerautomate-failedtofetch for more details."

Was this reply helpful? Yes No
Omardith20 43 on at

Like (0)

Report
Copy link

Link copied!

Any update on this one? Also encountering the same issue. Flows are running smoothly but when I tried to edit and save it, it prompts the error.

Thank you

Was this reply helpful? Yes No
Rokazas001 13 on at

Like (0)

Report
Copy link

Link copied!

We are also facing the same issue.

Was this reply helpful? Yes No
djshawy 17 on at

Like (0)

Report
Copy link

Link copied!

Same issue here

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Same issue, highly impacting workflows.

Was this reply helpful? Yes No
orphiucus 2 on at

Like (0)

Report
Copy link

Link copied!

Same issue here for an Excel Business Online connector - Flow still works but can't edit it - but other bot accounts and tried asking other people to try change it are still able to. Is this account specific to whoever creates the flow?

Edit: Tried asking others to create new flows with Excel Online business actions - can't create due to this bug. Current flows are still running but the direct owner can't edit them.

Was this reply helpful? Yes No
metrognome 59 on at

Like (1)

Report
Copy link

Link copied!

Just adding my voice to the chorus.
Funnily enough, the PA Support homepage shows up all green stating that all of PA is functioning normally.
The even stranger thing is that looking at the connections tab in the details page they are all green ticks:
however once entering the classic editor there's red flashes galore:
Something's not right but unclear what exactly or how to clear it.
I tried removing and re-instating all connectors but they keep returning as invalid.
Going to the connectors list, they show up nice and green with frequently updated "last access" timestamps.

Was this reply helpful? Yes No