PowerApp Weirdness - Gateway timeout to 'europe.api.bap.microsoft.com' cannot create a new PowerApp or open existing - Error :The requested content at path /v3.20061.23.152576243/siena/default.html is not found

(6) Share

Report

Posted on by AndrewTS

Good day all,

We have run into a few issues.

Firstly, we are unable to export our dev app to be deployed into production. When we try to export we get the following error.

"The gateway did not receive a response from 'europe.api.bap.microsoft.com' within the specified time period."

I also tried to create a new PowerApp to test the export on a considerably simpler and smaller app, I cannot even create a new app.

The error given is
"The requested content at path /v3.20061.23.152576243/siena/default.html is not found"

I have also tried to open an existing PowerApp (which I was able to get into yesterday afternoon) also gives the same error.
The requested content at path /v3.20061.23.152576243/siena/default.html is not found

Any one else having the same issues?

We do have a ticket open with MS, but waiting for feedback still.

Cheers,
Andrew

Categories:

Building Power Apps

2020-06-11 09_49_...

powerapps.png

I have the same question (0)

All responses (7)

Answers (0)

Community Power Pla... on at

Like (0)

Report

One of our users have the exact same issue this morning. Apps they were working on worked fine yesterday and now don't. I myself am working okay so I'm guessing it's only affecting certain users.

Was this reply helpful? Yes No
VikasDadhich 22 on at

Like (0)

Report

The same with all users in our tenant

Was this reply helpful? Yes No
nev04 4 on at

Like (0)

Report

Also having this issue on our tenancy at the minute!

Was this reply helpful? Yes No
barakEl 3 on at

Like (0)

Report

We also have this problem this morning...

Was this reply helpful? Yes No
hiccup 153 on at

Like (0)

Report

I'm also having the same issue 😞

Was this reply helpful? Yes No
JManey 2 on at

Like (0)

Report

Had this error today for a few of our developers - turned out to be our firewall ssl inspection blocking something under *.powerapps.com - nothing changed our end so I assume something changed microsoft side or possibly the automatic "365" group on our firewall.

Cheers

Was this reply helpful? Yes No
VikasDadhich 22 on at

Like (1)

Report

The issue is resolved now and it was because of the version which microsoft deployed yesterday and it was causing issues. Now MS has fixed the issue.

Was this reply helpful? Yes No