Hi, I added some attributes to the collection and we have been waiting for about 2 hours now for the "processing" tom complete. I restarted the server but it didn't clear the error. Checking the appwrite logs, I found:
appwrite | [Error] Timestamp: 2023-10-31T10:49:31+00:00
appwrite | [Error] Method: PATCH
appwrite | [Error] URL: /v1/databases/:databaseId/collections/:collectionId/attributes/string/:key
appwrite | [Error] Type: Appwrite\Extend\Exception
appwrite | [Error] Message: The requested attribute is not yet available. Please try again later.
appwrite | [Error] File: /usr/src/code/app/controllers/api/databases.php
appwrite | [Error] Line: 246
Is there something I can do to "clear" this?
Appreciate some tips - any tips...🆘
At times the attributes take a long time to be created. Can you retry?
Well, if I'm on Appwrite Cloud, I can submit a ticket but I'm self-hosting. Fo those people who hit into this. We resolved it by deleting the collection and recreating it
this happens very often. I am getting "stuck" error since yesterday. deleting whole collection fixes it. but I think this is not a right solution.
if you're having this problem while self hosting, feel free to create an issue. Otherwise, see https://github.com/appwrite/appwrite/discussions/6464
[CLOSED] Stuck on attribute processing
its with cloud. stuck from 10 hours
create a separate post and provide detailed context
sure
Recommended threads
- Relation Question
How do I create a relation from table y to an others x.$id. in my example I have a users table where I use Appwrites unique User IDs and I want other tables fo...
- Unknown attribute type: varchar / text
Since the `string` type is deprecated I tried using `varchar` and `text` in some newer tables, but when running `appwrite pull tables && appwrite types ./src/li...
- Query.search limitation
Since `string` is deprecated I used `varchar`, and now I cant use `Query.contains` , so I setup fulltext index and started using `Query.search` the issue is `Qu...