Post-Mortem Analysis

Post-mortem analysis in Revnoxa gives you a detailed breakdown of any resolved incident - what it cost, how long it took to fix, and whether the same problem has recurred on the same ASIN.

Accessing post-mortems

Go to Post-Mortem in the sidebar. You'll see a list of all resolved incidents sorted by resolution date, newest first. Use the search bar to find a specific ASIN or SKU. Click any incident to load its post-mortem.

What the post-mortem shows

Total Loss - the total estimated revenue lost during the incident, calculated from the ASIN's average daily revenue multiplied by the duration the incident was active.

Revenue Recovered - the revenue that has been recovered since resolution. As your listing returns to normal performance, this number grows - showing the real-world impact of resolving the incident.

Time to Detect - how long it took Revnoxa to detect the problem after it started. A consistently high detection time on a particular incident type suggests your polling frequency or rule threshold may need adjustment.

Time to Acknowledge - how long it took your team to confirm and take ownership of the incident after it was detected. This reflects your team's responsiveness.

Time to Resolve - how long from detection to resolution. This is your team's total operational response time.

Duration - how long the incident was active from start to finish.

Timeline

The post-mortem shows a simple timeline with the incident start date, resolution date, and key milestones. This gives you a clear picture of when the problem started relative to when it was detected and fixed.

Regression detection

If the same ASIN has had multiple incidents in the last 30 days, the post-mortem displays a regression warning. Repeated incidents on the same ASIN often indicate an underlying catalog data issue, a supplier problem, or a repricing rule that keeps triggering the same violation. Use this signal to prioritize root cause fixes rather than just resolving the surface-level incident each time.