After Insert Business rule on sys_attachment table does not execute when records are created through an Inbound ActionIssue "After" Insert Business rule on the sys_attachment table runs when the user adds an attachment to the RITM.The same does not run when the attachment is added via inbound action.ReleaseAll releasesCauseDelay in Insertion and updation of target table in the sys_attachment tableResolutionLet’s walk through the flow of how an email is processed in ServiceNow: A user sends an email to ServiceNow. The email reaches the ServiceNow email server. An Email Reader Job picks up the email from the server and brings it into the instance, triggering the email.read event. If the email contains attachments, they are inserted into the sys_attachment table at this stage. Meanwhile, various inbound email actions and business rules are evaluated. If any conditions match, the inbound email action is executed, and the attachment is then associated with the appropriate target record. The target table for the attachment is only determined after the inbound email action finishes processing. Observed Behavior: Attachments are inserted into the sys_attachment table before the corresponding inbound email action is processed. This means that when an after-insert business rule runs on the sys_attachment table, the table_name field (which indicates the target record) is still empty. As a result, the condition in the business rule fails and the rule is not triggered. Proposed Solution: Rather than using an after-insert business rule on the sys_attachment table, we recommend using an after-update business rule with the necessary conditions. This ensures that the rule is triggered only after the attachment is properly associated with its target record, following the processing of the inbound email action.