Changelog

Filtering is now supported in the Console and State tabs of the Debug Tools.

Users can filter logs and states using any free text, negation, regex, or exact phrases:

• Free text: Matches any string.
• Negation: Prefix with - to exclude a match. For example: -error
• Regex: Use slashes for regex. For example: /^foo/
• Exact phrases: Wrap multi-word strings in quotes. For example: "query failed"

You can combine filters using spaces (e.g. "query failed" -/error/ success).

The Offline Assets app setting and PDF Viewer component are now generally available on Retool Mobile. You can use the PDF Viewer to upload and view files from URL, Retool Storage, Offline Asset, or JavaScript.

Using the Offline Asset PDF source allows you to store PDF files that can be retrieved and viewed offline, or in situations where internet connectivity is limited.

Retool made internal improvements that streamline the way we save and store your app saves, resulting in quicker app load times for users.

These improvements are automatically applied to customers on Retool Cloud. If your organization is self-hosted, run the following shell command in your backend container to remove old entries for apps that have been deleted and compact data from app edits older than a month:

./retool_backend --run-pagesave-compaction

Run this command as often as necssary to clean up your database.

If your organization uses Source Control, Retool sometimes creates an automatic commit, called a catch-up commit, which keeps your branches up to date. If you want to ensure that developers in your organization retain complete control of changes within their feature branches, you can now disable catch-up commits using the following steps:

1. Navigate to Settings > Beta and toggle on Show disable auto catch up commits setting.
2. Navigate to Settings > Source Control and click the Edit Settings button on the top right.
3. Toggle on the Disable auto catch up commits setting.

To avoid issues with catch-up commits and other merge control mechanisms, refer to Retool's Merge conflict prevention strategies.

An improved version of the File Input component for Mobile is currently available on Retool Cloud and on Self-hosted Retool 3.168.0 or later.

This includes:

• Multi-file support – Users can now upload multiple files at once instead of being limited to a single file.
• Blob URL exposure – The component now exposes blob URLs to the value property in the component state.

You can now select multiple components and edit them at the same time using the Inspector. Select multiple components by clicking and dragging a selection box around them, or by using / + click.

When bulk editing components of the same type, such as two Buttons, you can edit all properties of the component. When bulk editing different types of components, such as a Button and a Text Input, you can edit the properties shared by the two components.

Properties that differ between components are identified as Mixed in the Inspector.

An improved version of the Scanner component for Retool Mobile is currently in private beta on Retool Cloud and on Self-hosted Retool 3.173.0 or later.

This includes:

• The ability to restrict or select from multiple barcode symbologies to scan.
• The ability to select between Manual or Automatic scan modes.
• While scanning from the native app, there is a visual indication of what is being scanned (a bounding box) when hovering over a barcode, as well as a checkmark when a scan is successful.
• Scanner V2 does not have the autoClose property.

You can now convert legacy single-page apps to multipage without needing to leave the IDE. Navigate to the Pages tab, and click Convert to multipage.

If you change your mind and want to undo this change, navigate to the Releases and history tab and revert your app to the change before the Migrated app to multipage change.

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.

Retool now supports the Login Attempted Retool Event, which triggers after a user authenticates and before the login process is complete. You can use Login Attempted to trigger a workflow and execute custom logic, such as modifying user data or querying external resources.

Choose to present users with an error message, or redirect them to an app or URL.

You can only attach one enabled parent workflow to this Retool Event. Retool recommends that this logic remain lightweight, because this workflow runs synchronously in the login flow and blocks users from accessing their Retool account until the workflow finishes.