Missed-runner alerts
A missed runner is the one that got away: a token you saw called runs to a multiple of its call-time market cap. OCT can watch for exactly that. Configure it in the missed-runner panel of Settings → Pushover (it’s independent of whether Pushover itself is enabled).
Turn it on
Section titled “Turn it on”Enable missed-runner monitoring, then set:
- Deliver via — Toast (in-app only), Pushover (phone only), or Both. (Choosing Pushover warns you if Pushover isn’t enabled.)
- Multiplier threshold — how far it has to run vs MC@call (1.25×–5×).
- Lookback (hours) — how far back a call still counts (1–168).
- Cooldown per token (hours) — how long before the same token can alert again (1–168).
- Min MC@call (optional) — ignore tokens that were called below this market cap.
How loud it gets
Section titled “How loud it gets”- At most 3 alerts per check (every 3 minutes). If more tokens qualify at once, you hear about the biggest movers; the rest go quietly onto cooldown.
- No backlog blast. The first time OCT checks for you, runners already in your lookback window are noted silently rather than sent all at once.
OCT does not look at your own wallets, so a token you already hold can still alert. Keep the site open if you want toast delivery.
Test it
Section titled “Test it”There’s a test on a token tool: paste an address, optionally force send (ignoring the multiplier and cooldown), and run it. You’ll get diagnostics — MC@call → MC now, the multiplier, and the multiplier needed. The test never writes a cooldown, so you can run it freely.