Discord Error Monitor Troubleshooting

The Plugin Disables During Startup

Confirm both config files were generated and load successfully.
Check the console message immediately after discord_error_monitor:.
Confirm mode is exactly webhook or channel.
Webhook mode requires a valid Discord webhook URL when enabled.
Check all numeric limits and the language color format.
Confirm the attachment filename contains %id%.

Webhook Reports Do Not Arrive

Confirm enabled is true and mode is webhook.
Verify the webhook still exists and its URL was copied completely.
Check AthenaBot logs for the Discord HTTP status returned during delivery.
Regenerate the webhook if it was deleted, rotated, or exposed.

Channel Reports Do Not Arrive

Confirm mode is channel.
Assign discord_error_monitor through /setup.
Grant View Channel, Send Messages, and Embed Links.
Grant Attach Files when full stack files are enabled.
Confirm the configured channel still exists and is sendable.

A Specific Error Is Missing

Check whether its exact message is in suppressed_errors.
Suppression is active only while debug mode is off.
A full queue drops the oldest pending report when max_pending is reached.
Check console warnings for a failed Discord delivery.

Reports Arrive Slowly During A Burst

rate_limit_ms intentionally spaces messages. Lower it carefully if the queue builds up, but keep enough delay to avoid Discord rate limits. Increase max_pending if legitimate bursts exceed the current queue size.

The Stack Preview Is Too Short

Increase max_stack_preview_lines up to 20.
Increase max_stack_chars within its valid range.
Discord embed-field limits still cap the rendered preview.
Enable include_stack_file only in a restricted destination when the fuller report is needed.

Dashboard Changes Do Not Match Local JSON5

Dashboard-backed MongoDB values can override local files. Make the change in the dashboard or confirm which source AthenaBot loaded before editing the JSON5 files again.