Migrations are marked as apply but they aren't applied.

This is a very serious issue, since we need to go through PROD and now have to verify that all the migrations that ran previously are actually applied or not.

### Version Information

Server Version:
v2.35.2-ce.cli-migrations-v3

### Environment
OSS

### What is the current behaviour?
I don't know what is causing it but I have a migration file that creates a view, it is marked as applied every time even on brand new instance but the view is never created.

### What is the expected behaviour?
Either the migration should fail or if it ran and is marked as applied then the view should exist.

### How to reproduce the issue?
I have no clue what is causing the issue since other migrations are running successfully.

### Any possible solutions/workarounds you're aware of?
Copy the same migration file and creating a new one.

No file, test, or entry point is identified in the report, and the reproduction is incomplete. Start by locating the migration runner and reproducing a fresh-instance migration that creates a view. Done means the migration either fails visibly or leaves the recorded applied state consistent with the view's existence.

Written by the indexing model from the issue text.