Publish and roll back web apps

An app release captures a built version for review and publication. Preview the candidate, confirm its API dependencies, and verify the live app after approval.

Prepare the candidate#

Save the intended visual-builder changes or commit the source for a Git-connected app. Confirm the selected target environment, build command, output configuration, and production branch where applicable.

Run the app's available checks and inspect build logs. A successful build proves the source can produce an artifact; it does not prove that sign-in, database reads, or business forms work.

Review in Releases#

Open Web Apps → Releases and inspect the candidate's source information, build result, preview, and any scan findings. Review the actions available to your role, including approval and publication.

Check these user journeys in the candidate:

• Landing page and direct navigation to a nested URL.
• Sign-in, sign-out, expired session, and denied access.
• A populated collection and an empty collection.
• Filter changes, paging, and refresh.
• A controlled form submission and a failed request.
• Narrow-screen layout and keyboard navigation.

Use fixture data for writes. A preview can still call shared services, depending on its configured environment and workflow bindings.

Coordinate workflow dependencies#

Confirm the app's API routes, request bodies, and response shapes against the intended workflow versions. A web app release is not a substitute for workflow release review. Do not include unrelated workflow drafts just because they exist in the same workspace.

Verify publication#

Open the live app in a fresh session and exercise its key interaction. Check corresponding workflow logs and app metrics. Confirm that clients are using the expected release and API environment.

Roll back an artifact#

Use the available release rollback controls to promote a known earlier artifact. This changes the deployed app, not its Git branch, source files, database contents, or completed external operations. Verify that the older app remains compatible with current workflow contracts and data before relying on rollback.