
Getting a 500 error in some of my collections, suspecting it's because of a relationship error caused by another collection that I have now deleted (but the error persists)

You might need to recreate the collection 😕
Btw, we worked on improving stuff like this and should be released on cloud in a couple weeks

Really? There's no way to restore/fix this?

How can I avoid that this happens in the future? These were my biggest/most important collections

Not really.

Does the stuck attribute cause any problems?
What's the 500 from?
Also, keep in mind relationships is experimental
Recommended threads
- Appwrite Sites and localStorage Problem ...
I'm currently struggling with the localStorage Problem and Custom Sites. My goal is to move our Flutter Web App to Appwrite Sites. When just deploying it I'm ...
- Relationship fields returning "$sequence...
It looks like today something changed in the backend, I have a project that has certain collections only accessible to teams with specific permissions. Sometime...
- Cloud Functions Executions partially dow...
Yesterday we reported a wide Function-Downtime. Today we have the same - just not wide-spread across all functions. DEV is down - Prod still working. Its the s...
