Skip to main content

​
Usage Tips

​
Use version history rollback

If your project has issues or you want to return to a previous stable state, use version history rollback. Use cases:
  • Recent changes broke functionality
  • Want to return to a previous stable version
  • Compare different version effects
  • Test different implementations
Steps:
  1. Go to your project’s version history page
  2. Review all version records
  3. Select the target version to roll back to
  4. Click “Rollback to this version” or “Restore this version”
  5. Confirm the rollback
  6. System will restore to the selected version state
Notes:
  • Rollback will lose all changes between current and target versions
  • After rollback, you can continue building from the restored state
  • If your project is connected to a database, watch for data compatibility issues
💡 Tip: Create version pins frequently so you can quickly roll back to stable states when needed.

​
Pin each known-good state

superun automatically records version history at each important milestone—no need to manually create version tags. How it works:
  • After you complete an important feature or make changes, the system automatically creates a record in version history
  • Each version contains the complete project state and can be viewed or rolled back anytime
Version History Best practices:
  1. After completing an important feature, test to ensure it works
  2. The system automatically saves the current state to version history
  3. View all milestone records in version history
Benefits:
  • Roll back to any historical version anytime
  • Easily compare differences between versions
  • Automatic project progress tracking—no manual management needed
💡 Tip: Version history is saved automatically. Just focus on development, and the system manages all version records for you.

​
Use version rollback when stuck in error loops

When your project is stuck in error loops or becomes messy, use version rollback to quickly return to a previous stable state. Use cases:
  • Messy project structure that’s hard to fix
  • Too many errors with high fix costs
  • Want to try a new approach, need to restart from a stable version
  • Need to return to a version where everything worked
Steps:
  1. Go to your project’s version history page
  2. Review all version records and find a stable version where everything worked
  3. Select the target version
  4. Click “Restore this version”
  5. Confirm the rollback
  6. The system automatically restores to the selected version state
  7. Continue development from the stable version
Notes:
  • ⚠️ Important: Rollback will lose all changes between the current and target versions. Proceed with caution.
  • If your project is connected to a database, check data compatibility before rolling back to avoid schema mismatches
  • After rollback, you can continue making new changes from this stable base
⚠️ Note: Check database connection compatibility before rolling back.

​
Troubleshooting

​
Unable to Operate After Historical Version Rollback

Symptoms:
  • Page cannot be clicked after rolling back from history
  • Right-side function menu disappears
  • Unable to perform any operations
Solutions:
  1. Check if it’s a Demo Version: Demo versions are read-only and cannot be operated. If rolled back to a demo version, you need to continue generating a development version
  2. Use Version History: If issues occur after rollback, you can roll back again to an earlier stable version
⚠️ Note: Historical rollback of demo versions requires continuing to generate development versions to operate normally.