EML_RX_CROSSORGReply linked to an issue in a different organisation
InfoEMLRetry: not retryable
An incoming reply referenced an issue that belongs to a different organisation than the inbox that received it, usually because a notification was forwarded from one organisation to another's support inbox. To keep organisations separated, the reply was not added to that issue and a new ticket was created in the receiving organisation instead. If this keeps happening between the same two organisations, review the forwarding setup.
When it is logged
- A reply to a ticket notification arrived in another organisation's inbox, usually because it was forwarded.
- The reply was opened as a new ticket in the receiving organisation instead of being added to the original.
What to do
- 1
No action needed for occasional entries.
- 2
If it repeats between the same organisations, review the mail forwarding rules involved.
Where you will see it
The code tags entries in the admin Log viewer, where you can filter by it and open individual occurrences. Codes logged as error or critical can also trigger a technical notification e-mail with the code in the subject:
Notification subject
[EML_RX_CROSSORG] [eml] …