Reset a Generated App Workspace
Applies to: App Generation projects that use the SaaS Engine template
The current project reset discards unsaved tracked source changes. It returns tracked files to the latest saved Git commit.
It does not return the project to its first generated version. Use rollback when you need an earlier saved version.
Before you reset
Save the current source when you might need it again. A reset cannot restore discarded tracked-file changes.
Review open editor changes and pending AI Engineer work. Stop active AI work before you reset the workspace.
Reset the workspace
- Open Edit via Chat.
- Open Version History.
- Select Reset Project.
- Review the confirmation.
- Confirm the reset.
- Reload the application preview.
- Test the affected workflow.
The reset changes tracked files only. Untracked files can remain in the workspace.
What reset does not change
Workspace reset does not change these items:
- database records.
- applied database migrations.
- uploaded files outside Git.
- environment variables or secrets.
- VM disk allocation.
- project billing.
- GitHub repository history.
The reset is not a database reset, VM rebuild, project deletion, or backup restoration.
Reset, rollback, restart, resize, and delete
- Reset Project discards unsaved tracked changes.
- Rollback makes an earlier saved code version current.
- Restart Service restarts the running application services.
- VM resize changes the machine capacity and preserves its active disk.
- Delete Project starts the project deletion process.
Normal restart and resize operations do not erase persistent disk data. Read Data Persistence and Backups.
If the application still fails
Check the current files, build logs, application logs, and recent migrations. Use rollback when a saved commit introduced the problem.
Do not use workspace reset as a database repair action. Use Troubleshooting AppWizzy Projects to identify the failing layer.