Hello,
We have checked your account and service status, and your service has now returned to normal:
- The
tainan-workforce service under your first created untitled project did indeed experience a deployment stall (that service has been deleted in our records).
- The
tainan-workforce service in the tainanhr project you recreated on 2026-04-08 03:54 is currently running normally: Pod is Running, 0 restarts, and it has been up for over 34 minutes. The server logs show that the "Tainan Workforce Inventory System" application is serving normally on port 8080 and is continuously updating baseline data.
In other words, the act of recreating the project resolved the issue itself, and no further action is needed at this time. Your service should be accessible normally.
Regarding the cause of the original stall & an important reminder:
Your project is deployed on your own Tencent SG project server (not a shared resource), so theoretically, you should not see "queued" messages. The "Upgrade to Developer plan to avoid queuing" message seen on the Dashboard is a suggestion for shared free nodes and does not apply to your current setup (you are already on the Developer plan + project server).
However, we checked your Tencent SG server, and it only has 2GB of RAM. It is currently using about 950MB, with about 1GB remaining. For Node.js builds + running online services simultaneously, 2GB is a very tight configuration. It can easily stall during the compilation phase or memory spikes, causing deployments to fail to complete. This is likely the root cause of the "stuck in queue" issue you encountered.
Recommendation:
- If you frequently need to redeploy or build larger applications in the future, we recommend upgrading this SG server to at least 4GB RAM in the server list (using the Resize feature on the Servers page).
- Alternatively, you can offload the build process to Zeabur's remote build (not building on this server) to reduce the load.
If you encounter any further issues, please feel free to reply. Thank you!
Forum