Issue Summary

In some cases where exceptions occur during the post-meeting processing of a meeting recap in AI-Powered Meeting Notes, Confluence will retry processing the meeting recap multiple times and can cause repeated notifications (push, email, in-app depending on settings) to users mentioned on the page. 

Steps to Reproduce

1. Enable Loom Meeting Recordings
2. Enable Meeting Notes in Confluence
3. Schedule a meeting with the same title as another meeting on the same day or a recurring meeting which has the same name as other content in the space where the meeting notes are stored
4. Have the meeting
5. After the meeting, Loom will send the meeting recap to Confluence and Confluence will handle duplicate page and folder name collisions but the will still respond with an exception which causes retries of the meeting ended processing
6. Mentioned users on the page will receive a notification (push, email, and/or in-app) for each retry.

Expected Results

Even when Confluence has naming conflicts or other recoverable exceptions, the post-meeting processing should not retry nor should mentioned users receive multiple notifications.

Actual Results

Mentioned users receive a notification each time the meeting ended processing is retried

Workaround

Configure meeting titles to not have a conflict with the name of existing folders and content in the destination Confluence where the meeting notes are stored