Duplicate incident updates generated by Inbound ActionIssue The issue may occur when for a single email there are multiple inbound actions triggering insert / update operations interfering. CauseIn this use case a custom inbound action was responsible for creation of a new incident, and there were few other inbound actions which were responsible for updating the incident. Moreover, the inbound action which was responsible for creation of incident did not have any qualification, meaning it would hold true for any of the incoming emails. 1. User sent first email, and it rightly created an incident. e.g - INC0172848. - You would see a log line as - Processed 'Create Incident', created incident :INC0172848 2. End user replied to an email which was sent as an notification upon creation of incident - INC0172848. 3. The email was received in the instance as type reply and it triggered the Inbound action which was responsible for updating the incident. - You would see a log statement as - Processed 'Update Incident', updated incident :INC0172848. 4. The inbound action selects - INC0172848 as target record for the transaction. However, since the inbound action creating the incident did not have any qualification, the inbound action also triggers and uses the same ID (INC0172848) as target record. Out of the box the Incident table does not have the column Number set as Unique.ResolutionIn order to avoid this situation, make sure all the inbound actions have proper qualification, so that each inbound action runs only for the intended emails. It is also recommended to set the column 'Number' as Unique for the Case / Incident table.