Web Developer
When removing a relationship in a DB, I'm getting a stuck tag on said entry, as shown in the attached screenshot. I'm confused as to what this means
Votes
1
Replies
21
Participants
Unknown
Messages
22
Web Developer
When removing a relationship in a DB, I'm getting a stuck tag on said entry, as shown in the attached screenshot. I'm confused as to what this means
Admin
Did you try to delete it while it was processing?
Admin
Are you on Appwrite Cloud?
Web Developer
nope
Web Developer
nope, this is a local self-hosted docker instance of appwrite
Admin
Can you check the docker logs for the appwrite-worker-databases container?
Admin
there should be some logs related to that attribute
Web Developer
Attribute not found[Job] (6553b327eb8d61.08949735) successfully run.Web Developer
despite it indicating the attribute doesn't exist, restarting appwrite still shows said attribute, inclusive the stuck label
Admin
Did you change anything about the attribute after creating it? Did you maybe delete the related collection?
Web Developer
i did re-deploy the related collection from the appwrite cli, that could be why - how would I go about removing the attribute in it's current state?
I have the same, also for the same reason (removed the respective collection and hence also want to remove the relationship).
How to get the attribute unstuck? I get a 400 when trying to create/update documents in the collection with the stuck attribute.
Relationships are taking forever to do anything.
Yah, it got stuck yesterday and is still stuck 😉
PS: Version 1.4.13 on cloud
Both cloud and shelf host have the same issue.
yeah I saw some other threads on this, but no solution so far?!
Admin
You're probably running into this issue: https://github.com/appwrite/appwrite/issues/6012
Admin
You would need to recreate the collection
Thanks @Drake 👍
PS: why wasn't the MR approved??? It would fix the issue. (I understand it can/should be fixed at the root cause of deleting the related collection, but the proposed fix would have solved it too, and so far the "better" fix is nowhere – not the best decision IMO)