Troubleshooting
Ticket Marked Resolved, But Nothing Was Fixed?
A fast escalation format for when support marks a ticket resolved but your issue is still happening.
Recent #help pattern: users get a "resolved" response while the original failure still reproduces. This guide gives you a clean, low-drama way to reopen with hard evidence so support can actually move it forward.
Key idea: don't reopen with a rant. Reopen with proof: same error, fresh timestamp, exact destination, and what changed since last attempt.
When to reopen vs. open a new ticket
- Reopen same ticket if it is the same root issue and still reproducible.
- Open new ticket if symptoms changed significantly (different error class or different product area).
- Cross-link both ticket IDs when unsure so support can merge context quickly.
2-minute repro protocol (before you reply)
- Run one clean retry (not 10 rapid retries).
- Capture exact error text and local time + timezone.
- Capture where it failed (dashboard, Discord DM, server channel, thread).
- Write one sentence: "Still failing after ticket marked resolved."
Copy/paste reopen message
Reopen Request — Issue Still Reproducible
Ticket ID: [existing ticket ID]
Status update: Marked resolved, but issue still reproduces.
Expected:
[what should happen]
Actual:
[what happened]
Exact error text:
[paste exact error]
Where it fails:
[dashboard / Discord DM / server / thread]
When tested:
[YYYY-MM-DD HH:MM timezone]
Fresh repro steps:
1) ...
2) ...
3) ...
What changed since last ticket update:
[container restart / key rotated / nothing changed / etc.]
High-friction mistakes that cause another "resolved" loop
- No ticket ID: support can't link prior logs quickly.
- No fresh timestamp: old evidence may point at a prior incident.
- Paraphrased error: "still broken" isn't actionable.
- No destination context: DM works but server fails is a major clue.
Avoid retry storms: repeated retries can trigger extra errors (rate limits, temporary locks) and make diagnosis slower. One clean repro is enough.
If this is affecting multiple users
Add one line in your reopen message:
Observed others reporting the same failure in the same time window. Please check if this is a platform-wide incident vs. account-specific issue.
This helps support route your ticket to incident triage faster.
Bottom line: reopened tickets get fixed faster when you provide fresh, exact, reproducible evidence—not longer explanations.