Errors
Key features
Unresolved error list
Errors shows recent unresolved failures created when features cannot finish because of Discord configuration, permissions, missing messages, or delivery issues.
Feature and failure context
Each error carries the feature, action, message key, timestamps, failure detail, and affected scope when the feature provides it.
Resolve from the dashboard
Admins can mark errors resolved after repairing the channel, role, message, permission, or feature configuration that caused the failure.
Global health indicator
The settings area shows the unresolved error count so staff can spot broken automation without opening every feature page.
Best for
Finding features that stopped working because a channel, role, message, or permission changed in Discord.
Giving staff a single place to review unresolved automation failures.
Separating fixed and acknowledged errors from issues that still need action.
How it works
A feature records an error
When a feature cannot complete an important side effect, it records an error with feature, action, origin, target, and failure details.
Errors shows unresolved failures
The dashboard lists unresolved errors and shows their count in settings.
Staff repair the root cause
Admins fix the missing Discord channel, deleted message, invalid role, permission issue, feature setting, or external delivery problem.
The error is resolved
Once staff have handled the issue, resolving the error marks it as handled. Repeated failures can create or reopen unresolved error state.
Setup checklist
Review the unresolved error count when opening settings.
Open Errors before changing several feature settings at once, so existing failures are not confused with new ones.
Use the feature name and failure detail to decide whether to repair a Discord channel, role, message, permission, or dashboard setting.
Resolve errors only after the root cause has been repaired or accepted.
Important notes
Errors is a dashboard troubleshooting surface. It does not create Discord messages or run feature actions by itself.
Resolving an error records that staff handled it; it does not undo the failed operation or automatically retry the original action.
Some admin actions resolve errors for the same activity scope when the underlying feature emits a successful follow-up activity.
Errors are feature-owned evidence. The best repair path depends on the feature that emitted the error.
Errors has no command reference and no bot permissions of its own; access is controlled by guild-admin dashboard authorization.
Troubleshooting
An error keeps coming back
The underlying feature is still failing. Check the feature named by the error and repair the channel, role, message, permission, or setting it references.
Resolving did not retry the feature
Resolve only marks the error handled. Re-run the original action, save the feature configuration, or wait for the next scheduled run if you need the feature to run again.
The error detail is not enough
Use the feature name, action, timestamp, origin, and target values as support context, then inspect that feature's settings and Discord permissions.
