🚀 Feature: Retry mechanism for function execution

[tuvaergun]

🔖 Feature description

I am experiencing data loss. This caused serious damage.
I want to run the Executions Appwrite functions again.

🎤 Pitch

There should be a feature that I can run again if there is an error. Or there may be a different feature such as if there is an error, try it for the 2nd or 3rd time after 1 hour.

There may be a manual retry button.
or custom definitions can be selected in the settings.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[tripolskypetr]

Also why do you connected CI/CD from main branch to the cloud? That's OK if we seeing some bugs cause It is beta but for the whole week my app is unusable

[safwanyp]

@tuvaergun This will probably require a re-work of the functions, to make sure that the function's execution payload is saved after the exec fails. I don't think it stores the payload for the execution right now.

---

@tripolskypetr Do you mean connecting your GitHub repo to Appwrite? Well, the branch is selected by you when connecting to GitHub while creating a function.

Keep in mind that while it does connect to main, you can make create a new branch in GitHub. When you push to this new branch, the function will build the code automatically. Since it's a branch commit, you will need to activate the build as an "active" deployment from the console.

[tripolskypetr]

@safwanyp Nope, the cloud is updating too often. Looks like spamming commits to the main branch which triggers CI/CD. For example, Realtime is down for several hours.

[tripolskypetr]

@safwanyp
Also, ELK stack for functions payload will be real good solution for @tuvaergun

[stnguyen90]

Related:

• 🚀 Feature: Error events #4646