In what order does prisma run migrations? Seems that in my cases it’s in reverse. I have two migrations and they fail because second which updates table is run before the one which creates the table.

This should not happen, can you provide a minimal reproducible example so that we can test?