Per title, it started after a failed relationship was created.
What to do?
It works if I create a new collection where the previously failed relationship does not exist.
Eg, in any collection where the relationship that failed to create I cannot access my documents data.
The attribute has now been removed from one collection. eg I can access the documents data once again. For some reason the attribute (relationship) vanished, I didnt do anything. However, the relationship is still present in the other collection and its status is "PROCESSING". Eg, I cannot access the data in those documents either.
Are you able to replicate the exact steps in any project?
I have replicated it with three seperate dummy collections with the same attributes. For some reason this relationship fails.
And doesn't go away when attempting to delete it.
This time on the seperate collections I did try and delete the "processing" attribute first which made both "stuck" instead of one going away and the other staying in "processing".
I tried different attribute names for the relationship, still "failed".
Great! Could you please create a GitHub issue with the steps needed to replicate the bug? That way the appwrite team will work to solve it π
It seems that the issue is that multiple many-to-many relationships fails. If I remove my previous many-to-many relationship it works.
Recommended threads
- Auto Updating Backend & Auth via Appwrit...
<@870607367597850624> Hey everyone π I wanted to ask to ask for a friend, heβs asking if Appwrite be used in a similar way to Supabase when integrated with AI ...
- execution failed
When executing an appwrite function, I'm getting a 500 error, but I don't see it in executions. This issue appeared today. Here's the appwrite function ID: 68b4...
- User Labels use Operator.arrayInsert(βla...
Can I use the new db operators on user labels or roles?