# EML_RX_FAIL: Incoming e-mail could not be persisted

- Module: EML. Internal e-mail subsystem (queue, dispatch, inbox)
- Severity: Error
- Impact: Operators. Organisation staff should take a look. Customers are not affected.
- Retry: Automatic. The platform retries or self-heals on its own.
- Reference: https://docs.bizkithub.com/en/system-codes/EML_RX_FAIL

## What happened

An incoming e-mail could not be stored after receipt from the provider. The provider may retry; otherwise the message is lost.

## Likely causes

- A received e-mail could not be saved after it was fetched from the provider.
- Message data from the provider was incomplete or malformed.

## How to resolve

1. Check E-mailer > Received for the missing message.
2. The provider sync retries on its next run; if the message is still missing, ask the sender to resend.
3. Contact support@bizkithub.com if entries repeat.

## Related codes

- EML_RX_SYNC_F: Incoming e-mail provider sync failed
- EML_RX_ATT: Inbound e-mail attachments could not be extracted
- EML_QUEUE_FAIL: E-mail queue write failed
- EML_RX_CLS: Inbound e-mail classification failed
- EML_RX_PARKED: Inbound e-mail parked out of classification queue
- EML_RX_QSTUCK: Incoming e-mail classification queue halted
