I think there should be a table generated with name as schema_info in
this table will have version as the column that contain the number of
the latest migration file you executed.
next time when you run migrations it will run all migration files
having number above the version number mentioned in schema_info table.
try to trace the schema_info table as above behavior.
try to trace it and