Appwrite functions break in patch versions of appwrite cloud

Appwrite cloud should not break in patch and minor versions.

First my functions started failing in both upgrade to 1.4.4 and 1.4.6. In cloud I should be informed at least 2-3 weeks ahead if an update is going to break something.

In 1.4.4 sync functions stopped running more than 30 seconds.

In 1.4.6 if a function is async now the body comes in the key body_raw instead of body part of req.

I will be thankful if informed about breaking changes 2-3 weeks ahead

sorry for the troubles you're having.

In 1.4.6 if a function is async now the body comes in the key body_raw instead of body part of req.

This might actually be a bug...we'll look into fixing this asap

I just want a way so that there is a process for upgrades and breaking changes.

Hey there 👋🏻 With latest release we introduced small bug to body parameter. We did pretty big patch change which caused it. Ill open an internal discussion to have release candidates for such scenarios to prevent unwanted bugs on Cloud.

Regarding 30sec sync execution limit, its nessessary devil to prevent some of downtimes kn cloud. Sadly some users abused this causing bottleneck for other projects. We are actively working on long-term solution to this bottleneck, so we can reenable long-running sync executions. In the meantime I would love to understand your usecase and see if we can solve it together.

Regarding 1.4.4 I dont exactly remember what bug was there so I cant comment on it.

With that said, I hear you. I hear lack of information regarding Cloud updates, and I hear frustration. Ill bring it up to make sure we improve on this front.

Thanks for the update. I am not against breaking changes or updates I understand that these are necessary. I just these to done in major versions or in a very well defined way. SO that we know that cloud is going to the next major fix everything until a specific date of things break. I am fine with that.

Thank you so much for your patience. This 30s limit was an urgent fix we had to release, and we'll definitely work to communicate such changes much better and do our best to avoid them from the start.

I can confirm the request body issue is a bug we introduced in the last version. We plan to release a fix for it today.

Thanks