Atttribute is still processing

That's the best part of the new migrations feature <:appwritefire:823999000330895380>

TL;DR

It seems that there is an issue with attribute processing in a support thread. The team is aware of the problem and is working on a solution. It is advised to keep an eye on a specific channel for updates. The issue will be temporarily mitigated and a permanent solution will be implemented in the future. The problem occurs when modifying the database structure, particularly when creating a new collection. However, it is mentioned that this should not affect the app after development is completed. The migrations feature is highlighted as a positive aspect. No specific solution is mentioned in the thread.

Well not really it errored a few times and it didnt really work but it was probably because of that it was stuck with processing that it could not create the documents because everything else did work

Mines been stuck in processing for a few hours already.

The most common scenario is that where you should not have to modify database structure

So the app should not be affected by that

Even creating a new collection?

The problem come when you modify database structure, so creating a new collection changes database structure and consequently you will face the problem

If you create a document, the database structure will not be changed

So in other words, it will not affect your app after it ends development

Anyways this issue will be solved soon

Yeah but you can't create a document on any collection if there is a pending update.

This isnt the first time I've had to wait for a day or 2 on a pending

But not temporarily, permanently. The team is working right now in a temporary solution, and after that, will work for the permanent solution

That's true, because you have modified database structure

As said before, after you finish your app development, database structure should not change in most cases 😅

(if you structure your database as SQL)

That's why despite Appwrite having a No-SQL database and being posible to use it as a NO-SQL database, I prefer using it as SQL, mainly because the underlying database is MariaDB/MySQL (SQL database)

Anyways, as said, the issue will be solved soon, and it will be mitigated to prevent it from happening again in the future by next weeks

||Maybe its good to make a announcement that there is something going wrong as you now have to repeat your message over and over again P||

Yes, definitely 😆

Well good luck ^^