#my database attribute stuck in processing and dont know what to do
1 messages · Page 1 of 1 (latest)
I think they are still working on it. Why not create a similer attribute and keep working with it?
Then when this is patched, you can delete the processing attribute later
lol i already try that, from 3 new attributes i created 2 new attributes have "processing" ....
when is the last time you tried creating attributes?
what's your project id?
like 20 mins ago. 6828a424001276991f00
hmm can you try recreating the attribute(s)? You might need to use the CLI or server SDK to delete the attribute
i deleted whole collection, with 3 "processing" attributes, and created new one, now i have 5 "processing" attributes....
weird...i can create them fine...
what are your exact steps?
wait same project or different?
6828a424001276991f00
what's the collection id?
6862e2e90025551c700d
the last created attribute i see was from an hour ago 👀
something like that, i already created the same collection 2 times, second time i got more "processing" attributes then in collection before. if i do it again it will be the same i think...dont want to create the same collection over and over
okey, i deleted and recreated collection again, now its okey
nice. FYI, we still have an ongoing incident on this.
Is there another solution than to remove the entire collection? I have many documents created in my collection so I dont want to delete it
By the way I think the issue only comes when setting a default value to a new attribute, I just created another attribute without setting a default value and I didnt have the issue