Notifications

Your message feed, and how it reaches you outside the console.

The bell in the header. Messages are filtered by kind — errors, warnings, successes and information — and you can mark all read or clear the feed.

What generates a message

Event	Kind
A job failed	Error
A job was refused at admission	Error
A watchdog finding on one of your jobs	Warning
A job finished successfully	Success
An export or evaluation completed	Success
Maintenance mode opened or closed	Information

Getting them outside the console

A deployment can mirror the feed to a chat channel, so nobody has to keep a tab open:

Channel	Configured with
Generic webhook	FORGE_WEBHOOK_URL plus a body template
DingTalk group robot	FORGE_DINGTALK_WEBHOOK_URL

Both take a list of which kinds to mirror, which exists to keep a shared group readable — mirroring every informational message is how a channel gets muted.

Outbound webhooks require the target host to be on FORGE_WEBHOOK_ALLOWED_HOSTS. Empty means no webhook may fire at all: the console can usually reach the internal network, so an unrestricted outbound target would turn it into an internal port scanner.

There is also a daily report — a written summary of the day’s post-training activity, sent on a schedule to its own channel. See notifications configuration.