"My SBOM uploaded but no alert appeared."
This is almost always expected, not a bug. Two common reasons:
- Zero purls matched. If your SBOM's components don't carry a resolvable purl, or none of them match anything in the current advisory feeds, there's nothing to alert on.
- Every match was Tier B or C. Only Tier A raises an alert, by design. Tier B shows in your inventory and the weekly digest; Tier C shows in your inventory only. Check your product's component list for matches that didn't reach Tier A before assuming the upload failed.
See Understand your first alert for how tiers are assigned.
"My case shows overdue but I already filed."
A stage can only be marked submitted with an SRP reference number or a note explaining an offline filing. If you filed but didn't enter one of those two things, the case has no way to know the filing happened, and keeps showing overdue.
Fix: open the case and enter the missing SRP reference or offline-filing note — not a support ticket. See What to do if you're already overdue.
"A VEX statement I filed didn't close my alert."
Expected if the alert was already open before the VEX statement arrived. Declara
deliberately does not let a VEX statement retroactively close an open alert, even
one with status not_affected or fixed — see
Why VEX suppresses a match but never an open alert
for why. Close the alert through its own triage flow instead of resubmitting the
statement.
"I need to correct a report I already submitted."
There's no amendment or edit feature for a stage that's already been marked submitted. The workaround is to carry the correction into the next stage's report — note what changed, the same way the SRP's own multi-stage design expects information to be updated across stages rather than edited in place. There is currently no way to reopen a submitted stage in the product.