Review and promote published workflows from Dev to Prod, including an automatically included function dependency. Check release history and test the promoted result before enabling the new route.
Watch tutorial (5:43)Move a reviewed set of published workflows from a Dev workspace to a Prod workspace. Releases let you review the changes together, keep a release history and review a rollback if you need to restore the previous workflows.
Use two existing workspaces in the same organization: a source labelled Dev and a destination labelled Prod. You must have access to both. Workspace limits still apply; Releases does not create extra workspaces or increase your allowance. If no eligible Prod workspace is available, open Manage workspaces to review your existing workspaces. If your current allowance cannot accommodate both workspaces, use View plans to review your options.
This example explains that the workspace limit has been reached. Releases still needs an existing Prod destination.
Publish and test the source workflows first. A release uses their published version, so unfinished edits stay in Dev. Resolve any unfinished destination edits before reviewing a release.
Open the Dev workspace and choose Releases in the sidebar. Choose a Destination workspace, select the workflows and optionally enter a Release note. Select Review changes.
You can include endpoints, server functions, middleware and event workflows. Required workflows are included automatically. When a workflow uses a table, a compatible table must already exist in Prod. Resolve any missing or ambiguous dependencies before continuing. If a workflow uses global variables, Prod needs the same names and types; its own saved values remain in place.
If a workflow uses secrets, configure the required names in Prod's Globals & secrets manager before reviewing the release. Review reports missing or unconfigured secrets without showing or copying values. A rollback also keeps Prod's current secret values. See Globals & secrets.
This first version cannot promote workflows that contain saved connected-account, external-database or API-request credential references. The review explains these blockers. Creating a matching connection in Prod does not map those references automatically.
The review lists added, updated and unchanged workflows. Expand an entry to compare its current Prod definition with the release. Summaries identify changes without revealing saved private values or credentials. Review the list of items that stay in Prod as well.
Select Promote release, then confirm the reviewed changes. A confirmation appears in the bottom notification bar after promotion succeeds. The selected workflow definitions change together. A running request keeps its consistent set of workflow definitions; new requests can use the promoted definitions.
Existing Prod endpoint access settings and event schedules stay in place. New endpoints remain disabled and new events remain inactive until you review and enable them. Check the promoted workflow with sample data before enabling a new endpoint or event.
A release or rollback review expires after 30 minutes. If the review expires or a source or destination changes, review the release again. Do not assume an interrupted request succeeded or failed: check Release history before trying again.
Open the Prod workspace and choose Releases. Release history shows its latest 50 releases. Automatic rollback is available for releases that only updated existing workflows. A release that introduced new workflows explains why automatic removal is unavailable. New endpoints and events stay disabled or inactive until you review and enable them.
In this example, the release added new workflows, so Review rollback is unavailable. The message explains why.
Select Review rollback for an eligible update release, check what will be restored, then select Roll back release and confirm.
The comparison shows the current Prod definition beside the version to restore. Private values remain hidden.
After a successful rollback, the confirmation and Rolled back history entry show what happened. Check this history if a request was interrupted.
Rollback restores the workflow definitions saved before that release. It is blocked if affected destination workflows have changed since promotion. Discarding or reversing a later Prod edit does not make that older rollback available again. Prepare a new reviewed release instead. This version does not automatically remove workflows introduced by a release. Review those changes first instead of overwriting later work.
Releases do not move or restore database records, table layouts, indexes, database triggers, credentials, global values, workspace settings or event schedules. Rollback does not undo emails sent, records saved or other actions already performed by a workflow. Prepare any required tables and global variable names and types separately before reviewing a release. Workflows with saved service credential references are outside this first version.
An ordinary Publish updates one workflow in its current workspace. Copy resources creates separate copies. Releases is the reviewed Dev-to-Prod flow for updating a coordinated set of published workflows.
Useful guides: Publishing changes, Testing, Middleware, Workspaces.
Realtime channels
Send live updates to your app while your customers are signed in. Use a channel for order progress, notifications or a shared activity feed, instead of asking the app to repeatedly check for changes. Realtime messages are temporary notifications. Keep important information in your database so your a...
Test suites
Test a customer journey across several endpoints in a single ordered run. For example: sign in, create an order, retrieve it, then check its status. Every run shares its own isolated database across its steps. Your workspace records are not changed by those database actions. This version supports is...
Data Types
Twidget supports six main data types to facilitate interactions within the platform. These data types are essential for defining inputs, outputs, and table fields, helping users understand the nature of the data being handled. The available data types in Twidget are as follows: Text. - Description: ...
Background jobs
Let a server function continue in the background while the original workflow returns a job ID. This is useful for work such as preparing a report or processing a batch of records. What counts as a job?. A function or endpoint is not automatically a background job. A job is created only when a workfl...
Command Output
Some commands in Twidget return outputs, which are essential for dynamic and conditional logic within your workflows. These outputs are displayed next to the command and are prefixed with an "as" to indicate the variable name. Using Output Variables. Once a command returns an output, you can use the...
