Keep delivery visibility separate from journal evidence.
Discord can surface important events without pretending that delivery proves the journal was updated.
Direct answer
What do Discord alerts do in SignalShield?
Discord alerts help notify the trader when important SignalShield events need attention, such as setup tests, warnings, cooldowns, locks, or delivery failures. Discord delivery is notification evidence, not proof that a journal record was written.
Traders who need important discipline events surfaced outside the app without turning Discord into another signal feed.
Next decision
Choose which warnings, cooldowns, locks, and delivery failures deserve notification visibility before enabling Discord.
How it works
Status first, evidence second, review always.
01
A SignalShield event is processed server-side.
02
If Discord is configured, SignalShield can request a notification for visibility.
03
Delivery success or failure is tracked separately from journal-write status.
04
The app should show Discord Connected only when explicit Discord delivery/test evidence exists.
Evidence and boundaries
What must remain visible for the feature to be trustworthy.
Discord skipped should not appear as Connected.
Generic account events should not create false Discord connection evidence.
Discord delivery failure should be visible without implying journal failure unless the journal write also failed.
Related discipline tools
Use one helper at the decision point.
These public helpers prepare rules, templates, and review notes. They do not write protected settings, change live system status, or replace server-side enforcement.
Does Discord delivery prove the journal was updated?
No. Discord delivery and journal persistence are separate states. A Discord message can succeed or fail independently of the core event and journal workflow.
Can Discord alerts execute broker trades?
No. SignalShield does not execute broker trades through Discord or any other notification channel.
When should Discord show Connected?
Discord should show Connected only when there is explicit Discord delivery or test evidence, not from skipped setup or unrelated account events.
Use the smallest useful workflow
Start manually. Add connected automation only when this feature solves a real problem.
