EML_RX_QSTUCK
Inbound e-mail classification queue halted
The classification queue aborted the current tick because the oldest unclassified e-mail failed to be triaged by the LLM. New inbound e-mails will queue behind it — no newer message is classified while the head-of-line row is unresolved. After the parking cap of retries the row is skipped and the queue resumes, but the underlying classifier problem should be investigated (typically an AI provider outage, malformed prompt, or exhausted quota).
What this code means
The classification queue aborted the current tick because the oldest unclassified e-mail failed to be triaged by the LLM. New inbound e-mails will queue behind it — no newer message is classified while the head-of-line row is unresolved. After the parking cap of retries the row is skipped and the queue resumes, but the underlying classifier problem should be investigated (typically an AI provider outage, malformed prompt, or exhausted quota).
Where you will see it
- In the subject line of technical-notification e-mails — for example
[EML_RX_QSTUCK] [emlHealthcheck] … - As a badge in the admin log viewer at
/log, where you can filter and drill into individual entries. - In the
core__system_logtable, stored against the code id fromcore__system_log_code.