> For the complete documentation index, see [llms.txt](https://dev.ubidots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ubidots.com/ubifunctions/specs-and-limits.md). # Specs and limits Keep these specs and limits in mind when developing with UbiFunctions. | Item | Description | Value | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | | Supported libraries | Libraries included in the Python and NodeJS runtimes for UbiFunctions. | [Supported libraries](/ubifunctions/runtimes.md) | | Code size | The maximum size of a UbiFunction's code, including all its files, compressed as a zip file. This limit can be increased upon request. | 4 MB | | File size | The maximum size of a single file in a UbiFunction, uncompressed. | 5 MB | | Concurrent executions | The maximum number of activations for a single UbiFunction that can be running or queued at the same time. This limit is fixed, but it can be increased upon request. | 1,000 concurrent executions | | Logs | The maximum size of a UbiFunction log. | 10 MB | | Memory | The RAM available to the computing resources used by a UbiFunction. `Full` runtimes get 1,000 MB by default. For the ML runtimes, we recommend at least 1,024 MB. This limit can be increased upon request. | 128 MB | | Rate limit | The maximum number of activations that can be submitted per UbiFunction per minute. API calls that exceed this limit return HTTP `429 Too Many Requests`. This limit is fixed, but it can be increased upon request. | 1,800 activations per minute | | Parameter size | The maximum size of the body or payload attached to a request. This limit is fixed and cannot be changed. | 1 MB | | Response size | The maximum size of a UbiFunction response. This limit is fixed and cannot be changed. | 5 MB | | Timeout | The maximum duration of a UbiFunction execution. This limit can be increased upon request, but it should never exceed 60,000 ms. | 40,000 ms | | Request headers | The maximum size of a UbiFunction request headers. | 8 KB | | Response headers | The maximum size of a UbiFunction response headers. | 4 KB | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://dev.ubidots.com/ubifunctions/specs-and-limits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.