Notifications
The bell icon in the top-right of every dashboard page is your inbox for things the system needs you to know about. It’s deliberately quiet. It doesn’t fire on every trade or every fill. It fires when something has happened to your positions that you should investigate.
What you get notified about
There are two notification types.
Position anomaly
The position-manager runs every five minutes and reconciles your tracked real-trade positions against what’s actually on-chain. When the on-chain state and your tracked state diverge, or when an on-chain operation fails, you get a position_anomaly notification linked to the affected position.
Reconciliation anomalies, in roughly increasing severity:
| Anomaly type | What happened | What to do |
|---|---|---|
| appeared | An untracked position showed up in your wallet for one of your automation’s markets. Usually because you (or a connected wallet) bought outside Airavat. | Check the position. If the wallet had a holding before the automation existed, the system auto-classifies it as pre-existing and dismisses it (you’ll still see a blue appeared badge with an explanatory tooltip). If it’s a recent unexpected entry, investigate the wallet. |
| grown | The on-chain balance is larger than the automation’s tracked balance. | Likely a manual buy or transfer in. Confirm intent; the automation will keep tracking the larger balance going forward. |
| shrunk | The on-chain balance is smaller than the automation’s tracked balance. | Could be a manual sell, transfer out, or a partial fill the system didn’t catch. Reconcile with on-chain history. |
| disappeared | The position is gone on-chain but tracked as open. | Most likely a manual full-close or transfer out. The automation will mark the position closed at the last known price; verify if PnL accounting matters to you. |
You’ll also get a position_anomaly notification when a market resolves but the on-chain redemption fails after multiple retries (logged as a redemption_failed entry in the trade activity log). That’s usually a transient gas/RPC issue. The system stops auto-retrying, so you may need to redeem manually on Polymarket.
The notification carries a deep link to the affected automation and position. Click through to see the full anomaly badge on the position row, plus the trade-activity log entry with technical detail.
System
Operational messages from the platform, usually about access changes, planned maintenance, or important policy updates. Rare. Marked with a system tag instead of an automation link.
How the bell behaves
- Unread count badge on the bell icon. The number is the unread count fetched on page load and updated live via WebSocket as new notifications arrive.
- Click the bell to open the recent-notifications popover (most recent 10). Each entry shows the title, message, and timestamp, with a click-through to the related position or automation.
- Live updates: new notifications arrive in real time via WebSocket. You don’t need to refresh the page. The WebSocket connection uses the same reconnect policy as other live features (10 attempts, exponential backoff from 2 seconds to 30 seconds). If the connection drops and recovers, notifications resume automatically. If reconnection fails after 10 attempts, refresh the page to restore live updates.
- Marking as read: clicking a notification opens its target page and marks it read. There’s also a “Mark all read” button in the popover header.
What you don’t get notified about
- Routine fills, scale-ups, or follow-sells. Those are visible in the automation’s Trade Activity tab; flooding the bell with every trade would make the meaningful events invisible.
- Filter matches that are skipped by the automation’s position limits. Those are aggregated as skip counts on the automation’s state, not surfaced as notifications.
- Throttled or zero-fill events. Same reason.
When to expect noise vs silence
The notifications system is biased toward silence on healthy automations and noise on anomalies. If everything is going smoothly, the bell will rarely light up. The first few real-trade automations you run, you may want to peek at the bell occasionally just to confirm, but the goal is that you don’t have to.
If you’re seeing repeated anomalies on the same automation, that usually means either:
- The wallet is being touched outside Airavat (manual trades, transfers in/out)
- A market is misbehaving (Polymarket-side resolution oddities)
- Or something in the trader’s behavior is breaking the position-manager’s assumptions. Worth flagging at support@airavat.xyz so we can investigate.