fix(#251): prevent startup crash when database migration fails on sta…#315
Merged
Conversation
…ging ## Summary If MigrateAsync() throws at startup (e.g. transient DB connectivity issue, schema mismatch on staging), the entire process was crashing before UseCors ran — causing 503 on ALL endpoints and no CORS headers on any response. Wrap MigrateAsync in try-catch so the app starts and serves requests even if the migration step fails. The error is logged for ops visibility. ## Changes ### API - Program.cs: wrap startup MigrateAsync in try-catch with error logging
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ging
Summary
If MigrateAsync() throws at startup (e.g. transient DB connectivity issue, schema mismatch on staging), the entire process was crashing before UseCors ran — causing 503 on ALL endpoints and no CORS headers on any response.
Wrap MigrateAsync in try-catch so the app starts and serves requests even if the migration step fails. The error is logged for ops visibility.
Changes
API