Project restoration button in console

The project restore button in console is taking no effect, i have tried several times and still nothing, it gives same popup if i reload

TL;DR

The user forgot to check the server and missed messages, but after checking, everything worked.

Same here. My application is off since yesterday due to this bug 🥴

<@1318073933253054475> and <@659917748759166978> could you check in the browser console (devtools, open with Ctrl + Shit + I), in the network tab, if some requests fails or hang ?

if yes, could you please share informations about that request ? (url, request headers, request body if any, and response)

If there is any personal data, please hide them. Also in case it's a bug in appwrite side, also provide the Appwrite Project Id so the team can check bugs in your project

There are 2 requests failing

/project/platforms: returning "Server Error" with "general_unknown" type and version 1.9.5
/project: returning "User (role: guests) missing scopes ([project.read])" with "general_unauthorized_scope" and version 1.9.5

I login again and the modal that was saying that the project is inactive disappeared, but it doesnt work yet

Is this enough? <@493852865907916800>

it's probably cuz of the first request. looks like an error 500 (so appwrite side).

Could you share as well :

the complete URL (to know if it's region API or the cloud API)
The method used for the request
When does it shows ? (at load or when you click ?)
And your project id (as it's 500 it's possibly from appwrite side, so share your project ID, so appwrite team can look into the issue faster)

also after you login again, do you still have error in the devtools ?

Hey <@659917748759166978>, we're aware of this - team is working on a fix

cc <@972109928242249778>

cc <@1318073933253054475>

Hi folks, we identified the root cause of the issue, deployed a fix, and are seeing error rates return to normal levels. Our investigation also identified why this was not detected by our monitoring sooner. An internal cache masked the underlying issue, so it only affected a small portion of requests. Because the impact remained below our alerting thresholds, it did not trigger an automated notification.

Our team is going to continue monitoring the service closely to ensure everything remains stable. We appreciate your patience while we investigated and resolved the issue.