Email-to-ticket is reliable, but occasionally an inbound message can't be processed — a malformed email, an unexpected format, a transient hiccup. Instead of losing it, AspirePro captures it in the Failed emails queue so nothing disappears silently.
Find it under Tickets → Settings → Failed emails.
What lands here#
Any inbound message that throws an error while being turned into a ticket is saved here, with the sender, subject, and the error that occurred. Filing an email is all-or-nothing: a failure never leaves a half-made ticket behind, and the same email failing again (a redelivery, the next mailbox check) updates its row and attempt count instead of adding another. Filter by unresolved, resolved, or all, and by board, and search by sender, subject, or error text. Open a row for the full detail.
What you can do#
- Retry — reprocess the message. If it succeeds, it becomes (or updates) a ticket; if it fails again, the row stays with the new error. Retry brings back the whole email, files and embedded images included: it reads the email again from where it came from — the copy kept when it arrived by forwarding, or the board's Outlook (Microsoft) mailbox. If neither still has it, the row says how many files can't be restored; Retry then files the text, and the ticket names each missing file. If the mailbox that holds the email is waiting to be reconnected, Retry waits too, so the files aren't lost.
- Dismiss — mark it resolved when it doesn't need to become a ticket (spam, a duplicate, something you handled another way).
- Delete — remove it entirely.
Check this queue occasionally, especially after changing a board's mailbox or inbound settings. A short list here is normal; a growing one is a signal worth investigating.
Ask Prox#
Prox (and any MCP client connected to your organization) can work this queue too: ask it to list failed emails to see what's waiting and why, or to retry a failed email — the same retry the button runs, with the same audit trail.