Self-hosted Retool 3.334 and 3.300 stable updates
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
Updates, changes, and improvements at Retool.
Refer to the stable and edge release notes for detailed information about self-hosted releases.
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
Retool 3.391 is now available on the Edge release channel for self-hosted organizations.
Organization admins in the admin space can now view audit logs from all spaces on the same instance directly from the Audit logs page. Use the Space filter to view events from a specific child space, or select all spaces to view events from every space at once. When viewing events across spaces, each entry includes a tag indicating which space it belongs to.

Users in child spaces continue to see events from their own space only, and downloads remain scoped to the current space.
For more information, refer to View audit logs across spaces.
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
Retool 3.387 is now available on the Edge release channel for self-hosted organizations.
The new Analytics page gives you visibility into workflow health and activity across your organization.
From the workflows landing page, select Analytics to access two views:
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
Retool 3.383 is now available on the Edge release channel for self-hosted organizations.
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.
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.