Rank 2: Process
Per title, it started after a failed relationship was created.
What to do?
Votes
0
Replies
12
Participants
Unknown
Messages
13
Rank 2: Process
Per title, it started after a failed relationship was created.
What to do?
Rank 2: Process
It works if I create a new collection where the previously failed relationship does not exist.
Rank 2: Process
Eg, in any collection where the relationship that failed to create I cannot access my documents data.
Rank 2: Process
Rank 2: Process
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?
Rank 2: Process
I have replicated it with three seperate dummy collections with the same attributes. For some reason this relationship fails.
Rank 2: Process
And doesn't go away when attempting to delete it.
Rank 2: Process
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".
Rank 2: Process
I tried different attribute names for the relationship, still "failed".
Rank 2: Process
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 😄
Rank 2: Process
It seems that the issue is that multiple many-to-many relationships fails. If I remove my previous many-to-many relationship it works.