Saving an embedded report fails the first time, works the second

[gotters]

We have an integration with power bi service, whereby we're embedding a report within our site.

We are generated a token server side, with edit capability, and using that to display the report.

Clicking - File -> Save on the report has been working fine.

Now, clicking File -> Save results in the error below - one I have never seen before "Credential Handling Error". However clicking Save a second time works without any failure (and the changes are actually saved, as confirmed by viewing the report in PBI Service).

Has anyone else experienced this? We have not made any significant changes and also given that a second save works it seems like there is something wrong on the PBI side?

Any suggestions are welcome!

[gotters]

it will be resolved next week... see here

https://powerbi.microsoft.com/en-us/support/

[gotters]

Started happening yesterday 4/16 at 11pm GMT +2 (at least that's when I noticed it but pretty sure it was not happening before then).

Also just noticed that it seems to be VPN related for me - if my VPN is off I dont get the issue, VPN on I get the issue.

And I think that the actual exception is related to a "/metadata/folders" api call that is happening along with the SAVE. This one

1. Request URL:
   https://wabi-us-north-central-h-primary-redirect.analysis.windows.net/metadata/folders
2. Request Method:
   GET
3. Status Code:
   403

The Save is returning a 200 but I see this exception in the console - although the error is different to the above popup message - the error is 

1. error: {code: "InvalidRequest", message: "Api isn't supported for profiles"}
1. code: "InvalidRequest"
2. message: "Api isn't supported for profiles"
   
   

When my VPN is turned off, i dont even see a call in the network tab to the metadata/folders endpoint.

Can you fix it 🙂

[aliabufoul]

Hello, I have a repro from my side as well. Would you be able to tell when the issue started to happen?
Thanks

[legendl]

Hi @aliabufoul ,
   I have the same error from my side. the requestId is 9e5502ff-c5c6-13fb-bcbb-26216b93a07d