Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hey!
As you’ve correctly noted, the timeout settings in your project.yml file are for runtime execution, not for the build time for remote builds. The build time limit for remote builds is different from the timeout configuration in your project yaml.
According to the Serverless functions limitations docs page, the maximum build time for remote builds is 2 minutes, which matches the error that you are seeing (120000 milliseconds is 2 minutes):
https://docs.digitalocean.com/products/functions/details/limits/
When you had fewer functions, you might not have hit resource or concurrency limits that are now being reached with more functions. This can cause deployments to take longer and potentially time out.
One option here is to try using the watch command instead of the deploy command:
doctl serverless watch . --remote-build
It will run until interrupted. It will watch the directory (which should be one you initialized for serverless development) and will deploy the contents to the cloud incrementally as it detects changes.
You need to run the command in a separate window and leave it running.
Let me know how it goes!
Best,
Bobby