Comments syncing multiple times in ServiceNow to Jira Bi-Directional integration SummarySteps to Stop Cyclic Updates in Jira-ServiceNow Bi-Directional Integration When using Jira-ServiceNow bi-directional integration, cyclic updates may occur. For example, when an update is made on the ServiceNow side, the same update might return to ServiceNow from Jira, causing duplicate updates. To prevent this issue, follow these steps: Modify the outbound flow to check the latest comment/work notes from Jira on the issue, add comment/work note to the issue only if the latest comment from Jira does not match that of ServiceNow's record. Modify the inbound subflow to check the latest comment/work note from the ServiceNow record, add a comment/work note to the record only if the latest from ServiceNow does not match with what is coming from Jira. Make use of the actions below to achieve the same 1) Look up Latest Comment on Issue - Jira Spoke 2) Look up Latest Attachment on Issue - Jira Spoke 3) Look up Latest Comment on Record - Utility Actions Spoke To manage comments effectively and avoid cyclic updates, follow these steps in the flow (ServiceNow to JIRA) Retrieve the Latest Comment from Jira: Use the action: "Look up Latest Comment on Issue". This action fetches the most recent comment from the corresponding Jira issue. Compare Comments: Check if the latest comments from Jira match the current comments you are preparing to send to Jira. Conditional Flow: If the comments match: End the flow. If the comments do not match: Use the action: "Add Comment" to send the new comment to Jira. Refer below sample flow screenshot : Additionally, after looking up the latest comment on the issue, add an additional condition to the if validation as shown below: To avoid cyclic updates when integrating Jira and ServiceNow, adjustments must be made on both sides (JIRA to ServiceNow subflow ) Please refer below screenshot :