Skip to content

Latest commit

 

History

History
34 lines (24 loc) · 2.91 KB

File metadata and controls

34 lines (24 loc) · 2.91 KB

Alert States

Alert notifications being sent depends on a few factors:

  1. The alert state of the check (e.g. “passing” or “failing”).
  2. The transition between these states.
  3. Your notification preferences per alert channel.

Alert rules

The following table shows all alert states and their transitions.

{% hint style="info" %} Note: The recovered condition is met if the prior test result was a failure and the most recent test result is a success. {% endhint %}

Transition Notification Error Severity Suggestion for User
✅ –> ✅ None N/A N/A All clear
✅ –> ❌ Failure Expected: “0x” High Investigate immediately. Frontend not creating expected smart contract interactions.
✅ –> ❌ Failure Test Timeout Medium Check test implementation if the error does not resolve itself in the next run
✅ –> ❌ Failure Strict mode violation Low Check test implementation as it may no longer work
✅ –> ❌ Failure Other Medium


❌️ –> ❌️ Failure
❌️ –> ✅ Recovery Expected: “0x” High Check DNS and deployments if no changes were made
❌️ –> ✅ Recovery Test Timeout Medium Test likely failed due to a temporary issue with the GuardianUI test runner. We apologize for the inconvenience.
❌️ –> ✅ Recovery Strict mode violation Low


❌️ –> ✅ Recovery Other Medium We will provide the error of the prior run that was resolved

✅ = passing

❌ = failing