The service is currently starting up even when there are errors in the migration process or while doing db connections

[surajit-zs]

It appears that the system shows "retrying SQL database connections" when encountering migration errors. However, it's unclear how beneficial this is. Instead, it might be more effective to exit and stop the app under these circumstances. In a production environment, this would trigger alerts when the pod restarts, allowing for quicker identification and resolution of the issue.