Send Web reques step not executing when triggered by issue creation in Jira Automation (Data Center)

[Alex Sander Albani da Silva]

Hi everyone,

I'm facing an issue with a Jira Automation rule in Jira Data Center. I have a rule that includes the "Send web request" action. When I test the webhook using the "Validate your webhook configuration" option, it works perfectly. However, when the rule is triggered by issue creation, the webhook step seems to be skipped or not executed at all — even though the rule shows as "Successful" in the audit log.

Interestingly, if I change the trigger to manual execution or scheduled, the webhook works as expected.

Additionally, I noticed that when I edit the rule, previous executions that were marked as "Successful" are now shown as "Canceled" in the audit log. Is this expected behavior?

Any insights or workarounds would be greatly appreciated!

Aditional info:
Jira Data Center v10.3.9

This is the rule:

This is the execution log when a issue is created and the rule triggered. Note that it stops in the "Re-fetch issue data":

And this is an exemple of log with the same steps, with a trigger other than "issue created". In this case the trigger was a Schedule and the web request was raised:

Thanks in advance!

[Bill Sheboy]

Hi @Alex Sander Albani da Silva -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

• What version of Jira are you using: Cloud, Server, or Data Center?  Your question states Data Center but is tagged as as Jira Cloud.
• An image of your complete automation rule in a single image for continuity
• Images of any relevant actions / conditions / branches
• An image of the audit log details showing the rule execution

Until we see those...

The audit log can show a rule execution as "canceled" when you try to run it in rapid succession from the editor after publishing changes.

Kind regards,
Bill

[Alex Sander Albani da Silva]

Thanks for your answer, Bill.

I added more information and images to clarify the situation.

Regards,
Alex

[Bill Sheboy]

Thanks for that information, and...

First, please move the Re-fetch Issue Data action to immediately after the Issue Created trigger.  That will help mitigate if there are any timing problems where the rule starts before all the data is ready / available for the remaining steps.

Next, in your Send Web Request action, did you select the option so the processing pauses until the call returns?