We couldn't load your data, Please try again later

[PaulPellegrini]

I've recently signed up for a power apps subscription (per user, per app, per month) and I was putting together some Dataverse tables to support my app. After creating my second table (yesterday), I can no longer see any Dataverse tables. I get this error message instead: We couldn't load your data, Please try again later.

I've tried in different browsers, and also in private browsing mode just in case it was a "clear your cache" kind of issue but no matter what I get this. It's been persistent for almost 24 hours, which is just so surprising.

Any thoughts on how I can proceed?

[Rutu01]

Having the same issue but only for one particular table

The error message is : 

Something went wrong.We weren't able to open your table. Try reloading or reopening.

There was an issue retrieving your most up-to-date data. Some features may not behave correctly until a successful connection is established.

It first happened when i tried adding a new column to this table. Neither can i see the new column, nor can i re add it as it gives a duplicate error ( So the column has been created somehwhere but is not seen) 

And since then i have the above error 😞

Have raised a ticket but lately it takes really long to get response 😞 Hope its faster this time

[GwendevBI]

Did you manage to solve this issue?

[Rutu01]

Hi Yes I published my solution multiple times/ refreshed multiple times. I'm not sure if that's the reason it resolved or if it would have resolved on its own. It resolved after a a day and a half . 

[dpoggemann]

Hi everyone, I have been having this exact issue in a couple environments as well.  It appears to resolve itself but I have not seen this before except in the past month or so.  Others?

[GwendevBI]

I agree, I only solved my issue by creating a new user in the Microsoft 365 account. I think this is a system error rather than anything that a user might have messed up. I initially thought that the issue revolved around the way i created the environment, assigned the license to the environment or my access level, but that's not the case. 
The issue is rather that it's a Microsoft error that can be waited out within 48h it will resolve itself eventually or ues a different account with the same privileges and access to continue.

[joost_romijn]

Same issue here, created a ticket with support.

[joost_romijn]

Somehow this magically resolved itself minutes after creating a ticket. After days of not working..

[rialjo123]

Publish both the table and the solution, then reload the table.  This worked for me.  As for most things Microsoft, it's best not to worry too much about why