Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Refer to the stable and edge release notes for detailed information about self-hosted releases.

77 posts tagged with "Self-hosted"

View All Tags

Configurable memory limits for workflow code execution on self-hosted instances

Admins can now configure memory limits for workflow code execution at the org level, and workflow editors can override those limits on a per-workflow basis.

  • Org-level defaults: In Settings, go to the Advanced section and click Advanced settings to set a default memory limit (MB) that applies to all workflow runs in your organization.
  • Workflow-level overrides: Open any workflow and go to Settings to override the org default for that workflow.

When a workflow runs a code block, the executor enforces the most specific limit available (workflow > org > server default). If a block exceeds its limit, it fails immediately with a clear error.

Customers who are not configuring limits see no behavior change — the server default of 2,500 MB memory applies. For customers whose workflows were hitting out-of-memory errors, limits can now be tuned without requiring infrastructure changes.

Deprecation of MongoDB 3.4 support

Retool is phasing out support for MongoDB Server version 3.4 and earlier. Organizations with an unsupported version of MongoDB Server connected to Retool must upgrade to MongoDB Server 3.6 or later.

  • For cloud organizations, support for MongoDB Server 3.4 and earlier has already been removed.
  • For self-hosted organizations, support for MongoDB Server 3.4 and earlier will be deprecated in the Q2 2026 stable release. It will be removed in the Q3 2026 stable release.

MongoDB Server 3.4 has been end of life (EOL) since January 2020. We recommend upgrading to a currently supported MongoDB release.