Project Rollback

What is rollback?

Rollback lets you revert your project to any previous deployment version. If a refinement didn't turn out as expected, you can go back to a version that worked — with one click.

How to rollback

In your project's chat view, each successful deployment appears as a checkpoint marker showing the version number, a description of what was built, and a timestamp. To rollback:

1. Scroll through your chat to find the deployment version you want to restore.
2. Click the Rollback here button on the deployment marker.
3. Confirm the rollback in the dialog that appears.
4. FloopFloop will restore your code and redeploy automatically.

The rollback button is hidden on the latest deployment (since you're already on that version) and while a deployment is in progress.

What happens during rollback

When you trigger a rollback, FloopFloop:

1. Retrieves the exact code from the target deployment version.
2. Replaces all current code with the older version (including removing files that were added later).
3. Triggers a fresh build and deployment with the restored code.

A new deployment version is created for the rollback (e.g., if you're on v3 and rollback to v1, the result is v4 with v1's code). Your deployment history is fully preserved.

Cost

Rollback is available on all subscription tiers, including the free plan. For paid plans, a rollback costs 1 credit. Free-tier users can rollback at no cost.

Limitations

• Database schema is not rolled back. Only the application code is reverted. If a deployment added new database tables or columns, those remain after rollback. This means rollback is best suited for UI, logic, and content changes.
• Only completed deployments can be used as rollback targets. Failed or in-progress deployments are not selectable.
• One rollback at a time. You cannot start a rollback while another deployment is already in progress.