I am trying to create an automation rule in confluence by using Attachment as the trigger.
However, the rule seems to run twice for a single file upload event, the second rule was 3 seconds after the first rule
Did anyone encounter this issue recently? It was working correctly few months back.
Hi @Agus Kanihatu ! Can you add some information about what this rule is? There are no changes in the list of attachments for the selected page? Is there only one attachment there too?
Ok, the rule is basically checking if the file has certain type/content and delete it (calling the delete attachment API) if it meets certain conditions. I tried to debug by removing the delete action, and there's no duplicate events.
I suspect there is a checking on the attachment action where it assumes the attachment was not successful because it was deleted, and it tried to re-attach again. The attachment Id is different for the 2 events.
My workaround for now is to introduce a delay after attachment event, to let it know the attachment was successful, then call the delete API. So far it seems to fix it.
It's just weird that this wasn't an issue since this rule has been running without issue for few months until recently.
I'm not sure if there's a better way, but at least I got it to work for now. Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Agus Kanihatu -- Welcome to the Atlassian Community!
I recall something like this symptom from a while ago but cannot find a defect for it in the public backlogs for Confluence, automation, or the ecosystem.
Are you on a paid Jira / Confluence license? If so, please work with your Site Admin to submit a defect to the support team to take a look: https://support.atlassian.com/contact/#/
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Bill.
I explained what I wanted to achieve in the other comment. It's probably not a bug, rather a feature for the attachment event. At least I have a workaround for it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.