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:

• All workflows: Aggregate run counts, failure rates, and resource consumption across every workflow in your organization. Includes a ranked list of your most-run workflows, a Top problem workflows table that surfaces workflows with high failure rates, and resource consumption data for the current month.
• Individual workflow: Drill into a single workflow to review summary stats, run and latency breakdown charts, resource consumption, and a paginated list of recent runs with per-run status and duration.

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.

You can now select the Python version used by a workflow from the Languages & Libraries tab. Click ... next to Python, select Update version, and choose between Python 3.10 and 3.14.

Python 3.14 does not include built-in libraries. When you upgrade, Retool automatically identifies any built-in libraries your workflow uses and installs them as custom libraries.

Python 3.10 will reach end of life on October 31, 2026. After this date, Retool will no longer support Python 3.10 in Workflows.

What's changing​

New and existing workflows on Python 3.10 will continue to run but they will not be supported. They will not be automatically migrated to a newer version.

How to upgrade existing workflows​

Python 3.14 is rolling out to cloud instances and will be available in an upcoming self-hosted release.

1. Open the workflow and go to the Languages & Libraries tab.
2. Click ... next to Python and select Update version.
3. Choose Python 3.14 and click Apply.

When you upgrade, Retool automatically identifies built-in libraries your workflow uses and installs them as custom libraries. Python 3.14 is mostly backwards-compatible, but Retool recommends publishing a workflow release before upgrading so you can revert if needed.

See Configure Python version for full details on how to upgrade and revert to a previously published release.

Timeline​

Date	Event
April 2026	Python 3.14 available
October 31, 2026	Python 3.10 End-of-Life (EOL); support removed from Retool Workflows

You can now delete workflows programmatically using the DELETE /api/v2/workflows/{workflowId} endpoint in the Retool REST API.

To use this endpoint, your API token must have the workflows:write scope. The endpoint only supports deleting standard workflows—deleting agents and functions via the API is not supported.

Refer to the Retool API reference for full endpoint details, including request parameters and error responses.

Retool made significant design updates to the workflows landing page to improve user experience and align more closely with the agents landing page.

The landing page displays all workflows, and folders containing workflows, for your Retool organization. You can perform the following actions from the landing page:

• Sort workflows by Name, Last Updated date, or Created date.
• Search for workflows.
• Toggle between Grid view or Table view.
• Refresh the workflows list.
• Import a workflow from JSON.
• Create a new Folder.
• Create a new Workflow.
• Create a workflow From Template.

You can now unpublish workflow releases from the Releases tab.

This feature is also available for workflows protected with Source Control. When unpublishing a release on a protected workflow, the latest saved version on the main branch will be live to users.

You can now unpublish workflow releases from the Releases tab.

This feature is also available for workflows protected with Source Control. When unpublishing a release on a protected workflow, the latest saved version on the main branch will be live to users.

You can now create a README from the workflow IDE to help clarify important information about your workflow for collaborators. For example, if a workflow requires certain permissions on a resource, or if it's only scheduled to run once a week.

This feature is also available for workflows protected with Source Control. To create a README, click the title of the workflow and add content to the Editor README field. READMEs are visible from the Edit workflow details dialog box, in workflows JSON exports, and in a markdown file from source control.

Enterprise customers can now use Source Control to protect workflow triggers. This prevents changes to a workflow's triggers without review. When you protect a workflow for the first time, triggers are now automatically included.

For workflows that are already protected, you now have the option to protect triggers using a new PR.

Once protected, triggers are versioned and published alongside each release. Information about your triggers is stored in the startTrigger.yml file in your Source Control repository.