Roll back safely

Code rollback, current data

Open Versions, choose an earlier version, and review the rollback. It creates a new deployment record pointing to the historical immutable artifact.

TeeAI checks whether the old version's tables, columns, and types are still available. Missing or incompatible structures block the operation. Extra current tables or columns are left in place.

No reverse database migration runs. No historical data backup is restored. Messages, tasks, preferences, and other business records created after the old release are retained.

After a rollback

Verify real behavior in Telegram. The latest development draft is not deleted or automatically replaced by the live version. Ask AI to fix the latest draft, or deliberately generate a new requirement, then review the resulting version before publishing.

If cloud state changed outside TeeAI, synchronize it by importing before further changes. Rollback never bypasses the revision conflict check.