Every finding in your Parsivex report has a lifecycle status. Status tells you whether an issue still needs attention, was intentionally excluded, or was fixed and verified. You control dismiss, snooze, and reopen; only Parsivex sets resolved when a successful re-scan confirms the waste is gone.
Statuses at a glance
| Status | Who sets it | What it means |
|---|---|---|
| Open | Default | The finding is active and counts toward your report's potential savings total |
| Dismissed | You | You marked the finding as "not an issue" — intentional staging, DR standby, or accepted cost |
| Snoozed | You | The finding is hidden until a date you choose, then returns to open automatically |
| Resolved | Parsivex | The finding disappeared on a successful re-scan because the underlying waste was fixed or removed |
Resolved findings show a verified badge with the resolution date. Dismissed and snoozed findings are hidden from the main finding list but remain in your scan history. On paid plans, use the Findings inbox to filter by status and manage lifecycle actions without opening each scan report.
User actions
Dismiss ("not an issue")
Use Dismiss when a flagged resource is intentional and you do not want to see it again.
- Optional reason text is saved with the dismissal
- Dismissed findings are excluded from your report's potential savings headline
- If the same resource is flagged again in a future scan, Parsivex carries the dismissed status forward — you will not be re-alerted for that resource and finding type
- If a dismissed finding disappears from AWS, Parsivex does not credit it as realized savings — you declared it was not waste
Snooze (hide until date)
Use Snooze when you plan to address a finding later but want it out of the way for now.
- Choose a date up to one year in the future
- While snoozed, the finding is hidden from the list and excluded from potential savings totals
- When the snooze date passes, the finding returns to open automatically
- If the finding is still present in the next scan before the snooze expires, the snoozed status carries forward
Reopen
Use Reopen on a dismissed or snoozed finding to return it to open.
- The finding reappears in your list and counts toward potential savings again
- You cannot reopen a resolved finding — resolution is permanent and tied to a verified fix
System action: resolved
Parsivex marks a finding resolved when all of these are true:
- A new scan completes successfully
- The finding was open or snoozed (not dismissed) in the previous successful scan
- The same resource and finding type no longer appears in the new scan
Resolution compares scans using a stable record of the resource and finding type across scans. The same EC2 instance flagged as idle in scan A and scan B is always recognized as the same issue.
When resolved, Parsivex:
- Marks the finding as resolved with the date it was verified
- Credits the finding's estimated monthly savings exactly once as realized savings
- Removes the finding from potential savings totals (it is now tracked as realized)
Rightsizing counts as resolution too — if an oversized EC2 instance is no longer flagged because you downsized it, Parsivex treats that the same as deleting the waste.
Parsivex marks findings as resolved only after scans that complete successfully. If a scan fails, Parsivex does not mark any open findings as resolved — even if you already fixed the underlying waste. Partial scan warnings do not block resolution; only a failed scan does.
How decisions carry forward across scans
When Parsivex runs a new scan, it matches findings to previous scans by resource identity:
| Previous status | Still present in new scan | What happens |
|---|---|---|
| Dismissed | Yes | Stays dismissed — not re-alerted |
| Snoozed (before expiry) | Yes | Stays snoozed until the date passes |
| Snoozed (after expiry) | Yes | Returns to open |
| Open | No (successful scan) | Marked resolved, savings credited |
| Dismissed | No | Stays dismissed — no savings credit |
| Open or snoozed | No (failed scan) | Stays open — no resolution |
This means your dismiss and snooze decisions persist across recurring scans. You do not need to re-dismiss the same staging server every month.
Where to manage findings
Dismiss, snooze, and reopen are available on your signed-in report. Open any completed scan from your dashboard or scan history, then use the ⋯ menu on a finding card.
Public share links are read-only — they do not include lifecycle actions.
Related articles
- Realized savings — How verified fixes become credited savings
- Severity and savings estimates — How potential savings totals are calculated
- How scans work — When findings are marked resolved
- Partial scan warnings — Incomplete scans vs failed scans