Reply email classified as new despire there is a valid in-reply-to headerIssue Reply email is classified as new even though there is a valid in-reply-to header which points to the message id of the original email which is tagged to a target record. This is occurred if customer sends an email and immediately him or someone replied on the same email. Both of these emails are created in the instance at the same time. ReleaseAllCauseEmail reader classifies the email and then the email is picked by the worker for processing. If the second email is processed before the first email, then the second email is classified as new if it is only relying on the in-reply-to header. As at this moment there will not be any email in the sys_email table with a target since the first email is not yet processed. For example a user sent an email to the instance and immediately replied to his own email. Email 1 Created at 2025-05-20 06:51:14Processing started at 2025-05-20 06:51:24Processed at 2025-05-20 06:51:25 Email 2Created at 2025-05-20 06:51:15Processing started at 2025-05-20 06:51:24Processed at 2025-05-20 06:51:25 In this scenario by the time the email 2 started processing, email 1 processing was not completed and there was no target record attached to email 1. Even though email 2 contains the message id of the email 1 in the in-reply-to header, its still classified as new.ResolutionThis is expected platform behaviour and there is no workaround. If the classification of the email is only relied on the in-reply-to header, there needs to be an email with the message id having a target record available in the instance, then only the instance will consider it as a reply. If two emails are sent back to back at the same time, we cannot control which email will be processed first at runtime.