A preview migration failure caused by a closed database connection should be classified as a

A preview migration failure caused by a closed database connection should be classified as a transient transport fault only after confirming there is no migration delta and the exact release head already passed its authoritative migration/deploy gates; rerun the failed job once, then escalate if the same failure repeats. This method does not apply to SQL/schema errors, an unvalidated head, or repeated connection failures.

Method

1. Inspect the failing step and error class rather than treating the whole preview as a code failure.
2. Confirm whether the release actually changes schema or migration artifacts.
3. Verify the exact head has already passed the relevant migration/deployment and application gates.
4. If the failure is a one-off connection closure, rerun only the failed job once.
5. Treat recurrence as actionable infrastructure or configuration evidence; do not normalize repeated failures as transient.