Error communicating with the API - Automation for Jira

[Shah Baloch]

I set up automation whenever a high-priority issue gets created in a project it should send a notification to a team in MS Teams. However, I'm getting the below error when the rule run.

Error communicating with the API

408 - {"errorMessage":null,"message":null,"warningMessages":[],"errorMessages":["Request timed out."],"errors":{},"status":408}

 Here is the JQL when it passes then it should trigger the notification:

project = "SUP" AND status = Open AND priority = High AND created >= -5m

Any idea why I'm getting the error and how can I fix it?

Thank you

[Andy Heinzer]

There is an existing bug we are tracking in regards to this behavior over in https://jira.atlassian.com/browse/JIRAAUTOSERVER-474

While we do not have a clear workaround for this yet, I'd recommend watching that bug ticket for updates to this.

[Bill Sheboy]

Hi @Shah Baloch 

Did you first setup things on the MS Teams side to receive things?  If not, please take a look that the steps in this documentation:

https://support.atlassian.com/cloud-automation/docs/use-automation-with-microsoft-teams/ 

Kind regards,
Bill

[Shah Baloch]

Yes, I followed the documentation I got the webhook URL from ms teams and that is the URL I'm using for automation.

[Bill Sheboy]

Thanks for that information.  

I have seen some reports of intermittent errors like that.  If it is consistently showing that error, please work with your site admin to submit a ticket to the Atlassian support team to see what they can find: https://support.atlassian.com/contact/#/

[Shah Baloch]

Thank you

[App Admin]

Did you ever find a resolution to this? 

[Shah Baloch]

No, I didn't find a proper resolution yet. I removed rules, regenerated a new webhook URL, and created the rule again. I still get the error when it triggers the first time every day. I mean after a first trigger it works fine for the rest of day, the next day I get the error again once it runs.

[Finnegan_ Brian]

I'm seeing exactly the same behavior and error code with Jira Automation and Webhook to MS Teams channel. 

[Jake C]

We have the same issue, anyone found anything on this?