#Rollback Function broke project

1 messages · Page 1 of 1 (latest)

blazing tundra
#

Hi Team,

Made alot of changes to a specific page on my site today and I'd made a mistake and used the rollback function to restore i minor change earlier and it seemed to have roll backed the entire days worth of work and adjusted the page layout.

Not sure whether this is just an isolated issue with the preview function however the changes I've previously made in the chat are not appearing.

Any further questions, feel free to reach out

Thanks

Job ID: 4880b76e-44ae-422b-8154-ba65cc970982
Page in question: https://vendorprofiles.preview.emergentagent.com/vendors/mock-3

kind isleBOT
#

Hi [User's Name],

Thanks for reaching out, and I understand how frustrating it can be to lose a full day’s work unexpectedly.

🔍 What Happened

Based on your Job ID 4880b76e-44ae-422b-8154-ba65cc970982, it looks like you used the Standard Rollback function. This type of rollback restores both the codebase and the chat trajectory to an earlier point — which is why your recent updates and layout changes are no longer appearing.

This behavior is expected as per our rollback design.

What You Can Do Now

  1. Check Your Code Files

Your changes might still be present in the underlying files even if the preview doesn't show them:

  • Click the VS Code icon in your Emergent editor.
  • Open the files where you made today's changes.
  • If the content looks correct, we can restore the preview without data loss.
  1. Restart the Preview Environment

If your code is intact but the preview isn't updated:

  • Open the VS Code terminal
  • Run: supervisorctl restart all (also can be done using agent by giving this prompt)
  • Wait 2–3 minutes, then refresh your preview URL
  1. GitHub Recovery (if used)

If you previously saved your work to GitHub:

  • Click the GitHub button in the UI
  • Open your repository/branch
  • Pull the latest commits and redeploy

A Standard Rollback performs a git reset to the selected commit and truncates both code and chat trajectory. This is working as intended — but can wipe recent changes if not saved beforehand.

How to Prevent This in the Future

To avoid losing work going forward:

  • Save frequently to GitHub using the "Save to GitHub" button
  • Use “Keep Code Rollback” if you only want to revert chat history
  • Fork chats instead of rolling back to preserve all code changes

If your code files are gone and you don't have GitHub backups, then you need to implement those features and changes again.

Best,
Emergent Team

blazing tundra
#

hey bro thanks for the tips, known of the tips worked unfortunately to recover the work i had. the rollback went too far even thouugh i recalled the llast change.