Workers and Time Limits
Every project has a Workers and memory section under Settings. It holds how much Odoo runs (workers) and how long Odoo lets a single piece of work run (time limits).
Odoo Workers
More workers means better performance for concurrent users, fewer workers means lower resource usage and cost.
On managed hosting the number of production workers follows your subscription, which provisions them in blocks of three. On Bring Your Own Server you size the deployment yourself: workers, cron workers, and the memory each process may use.
Worker settings size the production deployment only. Staging and development deployments always run as a single Odoo process on fixed CPU and memory, which cannot be configured.
Time Limits
Two settings bound how long Odoo lets work run. Both are entered in minutes, up to 120; leave a field at 0 to use the platform default of 15 minutes.
- Request timeout: the maximum time a single request (a page load, an app installation, an import) may run before Odoo aborts it. It sets both Odoo's real-time and CPU-time limits. Raise it for very heavy imports or migrations; lower it if you want runaway requests cut off sooner.
- Cron worker timeout: the maximum time a scheduled-action worker stays alive before Odoo restarts it, so a stuck scheduled action cannot block cron indefinitely.
Unlike the worker settings, time limits apply to every deployment of the project: production, staging, and development. Values take effect on the next deployment (build, update, or restart).
Free Sandbox projects always run on the platform defaults; changing these limits requires a paid plan. Only project admins can change them.