I think it was 2 weeks ago where something like this happened already.
And it is happening again, but the behavior is even more odd than the previous time many users reported this here 2 weeks ago.
The function "66ce83e790179967fbda" who's build time you see is at 46 min was the first build. Now its status is shown as "Building" but before I tried redeploying (the top one), it was in an "active" state, and the top right side was still in the "building" state. The size was 0 Bytes. But if one look at the log, At the very end, one can read "Build finished." and no error within the entire log.
At 20 minutes stuck like this, I tried redeploying it, which resulted in the top one, behaving exactly the same where:
- the build state at the top right and the build state at the deployment list are conflicting
- the log says the build have been completed
- the function is stuck in this conflicted state forever and cannot be used.
- the size is somehow just 0 bytes.
[SOLVED] Function build is stuck forever
Tried again, and it fixed itself. Not sure why this is happening, but everything is working again now.
Recommended threads
- Worker functions stuck on "Fetched 0 fun...
Appwrite Version: 1.9.0 Bug Description: The appwrite-worker-functions container gets stuck in an infinite loop logging "Fetched 0 functions..." while scheduled...
- I am using s3 for app storage but is it ...
_APP_STORAGE_DEVICE=s3 puts everything to the s3 storage but i need to be able to keep the function builds and site in the local and not waste the cloud storage...
- Local Serverless Function Testing: Are D...
I have followed the instructions to get the CLI working, and have been able to log-in, initialize my project, and created a simple Python function, which calls ...