Skip to main content
When a production deploy turns out to be broken, roll back in seconds.

​
How

1

Settings → Deployments

See the timeline of all production deploys.
2

Click any prior deploy → 'Rollback to here'

Confirm. Rollback executes in seconds.
3

Verify

Open production. The previous version should be live.

​
What rollback does

  • Reverts the frontend code to the previous deploy’s bundle.
  • Reverts the Convex functions (queries, mutations, actions).
  • Does NOT revert schema migrations.

​
Schema migration caveat

If the broken deploy added a priority field to tasks, rolling back leaves the field in the database but removes the code that uses it. The orphan field is harmless — old code paths don’t reference it; new writes don’t include it. For destructive schema changes (renames, drops), rollback is more involved. vly will warn you when a rollback is “schema-incompatible” and walk through the cleanup. To minimize this pain, deploy schema changes separately from feature changes when possible.

​
Promotion via rollback

You can also “rollback forward” — promote any past production deploy back to current. Useful when:
  • The current code is fine but data is wrong; restoring an old version doesn’t help.
  • A demo deploy was promoted by mistake; revert to last week’s prod.

​
Notifications

When a rollback happens, vly notifies the workspace owner via email. Audit log captures who did it and when.

Version history

Code-level rollback (per revision).

Staging vs production

Prevent issues from reaching prod.

Monitoring

Detect issues fast.
Last modified on April 18, 2026