Retool removed some JDBC connectors that were inadvertently included in certain self-hosted release versions. These include:

• Actian Ingres/Vector JDBC Driver.
• Clickhouse JDBC Driver.
• IBM Data Server Driver for JDBC.
• IBM Informix JDBC Driver.
• Trino JDBC driver.

These JDBC connectors are not supported by Retool for self-hosted deployments. If you have created a JDBC resource using these connectors, update its configuration as needed to make use of your own preferred JDBC drivers.

Retool has since released patch updates for affected releases that remove these connectors.

Customers with a 3.259.0-edge deployment should immediately update to 3.259.1-edge. This patch release addresses a security vulnerability that could expose environment variables during code-executor startup.

Self-hosted Retool 3.251 and later contain two notable changes to the code-executor service:

• A container running code-executor is required to run workflows and custom API authentication. Previously, these features could be run in a sandbox in the backend container. Retool's security team has become aware of a sandbox escape and will no longer be supporting sandboxing in the backend. For more information refer to the disclosure page.
• Traffic to the private 192.168.0.0/16 IP address range is blocked by default. If you want to disable this security configuration, follow the instructions in the code-executor security privileges documentation.

Retool removed the preview release of Agents for self-hosted organizations since Agents is now in public beta with the 3.234.0 edge release and it will be available in 3.253 stable. This preview release was intended for deployment into a non-production environment, and was created as a mechanism to allow Self-hosted organizations the opportunity to create agents prior to their availability in an edge or stable release.

Retool Agents is now in public beta on Self-hosted Retool 3.234.0.

To enable Retool Agents in Self-hosted Retool 3.234.0 and later, the AGENTS_ENABLED environment variable must be set to true.

A preview release of Retool Agents is currently available to self-hosted organizations for deployment into a non-production environment. This preview release is intended to allow customers to preview and create proof-of-concepts that show how agents may work in their environment.

As Retool is continuously working to develop and improve Retool Agents to meet the high standards required for production environments, this preview release is not intended for production use and this build should not be deployed in an existing Retool installation or deployment. Retool recommends that self-hosted organizations create a new deployment in a private network alongside resources to which you intend to connect. Retool reserves the right to make changes to the agents preview without notification.

The backend runtime in self-hosted Retool 3.163 and later has been upgraded to use Node.js v20.18. This change may result in memory and CPU usage of containers to increase. Without sufficient resources, this could impact the performance of Retool Workflows. If necessary, you can increase the memory limits for workflows using the WORKFLOW_MEMORY_LIMIT_MBS environment variable.

Retool's Slack integration now supports the files.getUploadURLExternal and files.completeUploadExternal APIs for uploading files. Slack ended support for their files.upload API on March 11, 2025, and this endpoint is no longer available in the Retool Slack integration.

For most users, no action is required to access the new APIs. For self-hosted organizations that set the SERVE_LOCAL_SPECS environment variable, you must upgrade to version 3.168.0-edge, patch release 3.148.2, or patch release 3.114.17 to access this change.

The workaround described in the Action Required: Update Slack queries using files.upload changelog entry is no longer required.

Slack is ending support for their files.upload API on March 11, 2025. Refer to the Slack changelog for more information.

Retool is working to update our Slack integration as quickly as possible. In the meantime, if you need files.upload functionality, you can use a REST Query to utilize the new files.getUploadURLExternal and files.completeUploadExternal APIs.

This workaround is temporary, and Retool will restore access to file upload functionality within the Slack integration as soon as possible. Another changelog post will be made when the ability to upload files is restored. Other functionality in the Slack integration remains uninterrupted.