We rolled back the migration, everything is alive. We need to deploy a feature — what will you do next if you just deploy again, and everything will repeat?

If everything worked after rolling back the migration, but the problem recurs when applying the migration again, you need to:

1. Analyze the cause of the error in the migration — perhaps the migration contains a bug or is incompatible with the current data schema.
2. Check logs and errors when reapplying the migration to understand what exactly breaks.
3. Create a new migration that fixes the problem, rather than simply reapplying the old one.
4. Test the migration in a test environment with a copy of the data to ensure its correctness.
5. Discuss with the team possible changes to the data structure or business logic that require migration adjustments.

You cannot just reapply the migration if it breaks the system. You need to fix the migration or the approach to data changes to ensure the feature works reliably.