Marc-André Bombeck 55bb5e9432 chore(schema): drop legacy consecutive_failures column on integration_statuses ...

v1.4.43 W14 introduced consecutive_failures_by_kind as the bucketed
per-FailureKind counter and kept the single-column consecutive_failures
integer for one release as a fallback for v1.4.43 readers mid-deploy.
v1.4.45 W10 closed the back-fill write gap so the bucket and the
legacy column post-write at the same N+1 value, and the >24h release
gap since v1.4.43 means every active integration in production has
written at least one failure or success, so every row's
consecutive_failures_by_kind is populated.

The legacy integer is now redundant: the alert ladder reads
Math.max over the bucket values and no other call site consults the
column. Migration 0076 drops it with an IF EXISTS guard. The
reversibility recipe is documented inline so a rollback can rebuild
the column from GREATEST(transient, reauth_required, persistent) over
the existing JSON payload.

2026-05-22 09:16:30 +02:00

..

migrations

chore(schema): drop legacy consecutive_failures column on integration_statuses

2026-05-22 09:16:30 +02:00

schema.prisma

chore(schema): drop legacy consecutive_failures column on integration_statuses

2026-05-22 09:16:30 +02:00