β[Help] Function stuck in "waiting" status after following Appwrite contributing setup
- 0
- Self Hosted
- Functions
- Databases
Hi Appwrite team π
I'm trying to contribute to Appwrite and followed the official setup instructions from the CONTRIBUTING.md guide to run the platform locally.
After spinning up the environment using Docker and accessing the Console UI, I tried creating a Cloud Function to test changes β but the function deployment gets stuck in waiting and never moves to building or ready.
What I checked and tried: Iβve read through all existing Discord Discussions and Issues that mention "waiting"
I also followed the suggestions from this Discord thread: https://discord.com/channels/564160730845151244/1072905050399191082/threads/1181481109939290122
I tried:
Pressing "Redeploy" on the stuck function
Creating multiple new functions
Uploading code using the "Manual Upload" option
Additionally, when I create attributes for a collection, they also remain in processing status and never become active
Questions: Do I need to do anything additional to enable function builds locally?
Should I manually pull runtimes from GitHub Container Registry (ghcr.io/open-runtimes/...)?
Are some background workers (like Functions or Database) not running?
Is there a way to check or trigger the queue/worker jobs manually?
Could I be missing some services, environment variables, or network permissions?
Any help or pointers would be really appreciated π
Thanks in advance!
β[Help] Function stuck in "waiting" status after following Appwrite contributing setup
Recommended threads
- My cloud functions failing 3 days ago (P...
Hi, My cloud function using python has been failing for 3 days, I didn't push any new deployments... Its something to do with it not recognising the entrypoi...
- Scheduled works locking the entire Maria...
I have a scheduled function and apparently that or something is locking the entire MariaDB database and Appwrite is giving MariaDB errors. This error persists e...
- Python Function not working
I am getting this issue as well. Doesnt look like there was a solution as you guys were not able to replicate. Below is my code as well as the error. I started...