Skip to main content
The Failed Transaction trigger alerts you any time a transaction directed at the monitored contract reverts or fails on-chain. Failed transactions often signal attempted exploits, misconfigured callers, or contract logic errors.

​
Use cases

Attackers frequently probe contracts with crafted calls that revert. A spike in failed transactions can be an early warning of a targeted attack.
Catch broken integrations or misconfigured bots that are sending transactions with wrong parameters before they cause downstream issues.
A regression in contract logic that causes previously valid calls to revert will immediately surface as failed transaction alerts.

​
Configuration

1

Trigger Name

Enter a descriptive label, e.g. Failed Transaction Alert.
2

Severity

Choose the alert severity: Critical, High, Medium, Low, or Info.
3

Notification Channels

Select one or more channels to receive the alert (email, Slack, webhook, PagerDuty, etc.).
This trigger has no additional filter fields — it fires on every failed transaction to the monitored contract. Use severity and notification channel settings to control alert routing.