I really can't answer why it happened. If for some reason, after migrating, it didn't put the migration name in the
migrations table, it would try to run it again the next time you migrated since it runs migrations that
aren't in the migrations table. I used to mess up migrations too in the beginning when learning and doing things the wrong way, but haven't had that issue in years.