Notifications
IPDA posts to the shared notification-service (POST /notifications),
the same service mt5-trader uses.
NOTIFICATIONS_ENABLED=true
NOTIFICATION_SERVICE_URL=http://127.0.0.1:3010
NOTIFICATION_API_KEY=...
NOTIFICATION_CHANNELS=TELEGRAM # TELEGRAM, EMAIL, SMS, WHATSAPP
NOTIFICATION_TIMEOUT_SECONDS=30Events
| Event | When |
|---|---|
signal_skipped_out_of_session | A Buy Chance / Sell Chance signal fired outside TRADING_SESSIONS and was not executed. One notification per candle, not per poll. |
break_even_reached | A filled trade reached the MFE trigger — see Break-even. |
The HTTP source field is ipda (or ipda.{profile} when --profile is set).
Failure isolation
A notification failure is logged as notification_failed and never interrupts trading.
The missed alert is not retried, but the underlying event remains in {LOGS_DIR}/signals.jsonl.
Execution-outcome alerts after mt5-trader accepts or rejects an order still come from the
mt5-trader profile when its own NOTIFICATIONS_ENABLED is on. IPDA only covers
session-skip and break-even advisories.
Related
- Sessions — what triggers an out-of-session skip
- Break-even — MFE advisory
- Operator runbook — how to handle each event
- notification-service — channel delivery
Last updated on