After relocating n8n 1.51.2 to a cloud SQL environment, why does the startup execute migration steps when the migration table already exists? I anticipated a routine startup without migrations.
In my experience after deploying n8n in a cloud SQL environment, seeing migrations run on startup even with a migration table present is typically due to the application performing integrity checks on the schema against its internal configuration. This behavior, though unexpected, acts as a safeguard to ensure the database structure is in line with what n8n expects, especially considering the differences in how cloud environments initialize connections. I observed that these extra checks are standard and idempotent, ensuring that no schema discrepancies exist. It is advisable to review environment settings and logs to confirm that migration processes complete successfully.