Rules
FP901 · override-expired
An override passed its `expires` date; the findings it suppressed are reported again.
| Code | Name | Category | Default severity |
|---|---|---|---|
FP901 | override-expired | Config & overrides | 🔴 error |
Why it matters
Overrides are meant to be temporary exceptions with an owner. An expired one means the follow-up work was not done and the original problem is back in scope.
How to fix
Fix the underlying findings and delete the override, or — if the exception is still justified — extend expires with an updated reason.
Example
overrides:
- rule: unused-input
target: .github/workflows/pipeline.yml#inputs.legacy-flag
reason: Read by the release dispatcher until the migration (JIRA-123)
expires: 2026-01-31Configure
Change the severity (or turn the rule off) in .github/flowpact/flowpact.config.yml, by code or by name:
rules:
FP901: off
# or: override-expired: errorExplain it in the terminal:
flowpact explain FP901