403 ERROR in web request to Jira inside an automation rule

[Juan Falguera]

I have an automation rule that grabs an information (reporter email) from the issue description during it's creation an sets a field on the same issue. 

To do that, I make a web request to the address: https://<mycompanyname>.atlassian.net/rest/api/3/user/search?query={{issue.description.match("([a-zA-Z0-9+._-]+@[a-zA-Z0-9._-]+\.[a-zA-Z0-9_-]+)")}}

This worked fine for a year, till last weak. 

Now I am getting the error: 

The request could not be satisfied

403 ERROR

The request could not be satisfied. Bad request.
We can't connect to the server for this app or website at this time.
There might be too much traffic or a configuration error.
Try again later, or contact the app or website owner. 
If you provide content to customers through CloudFront, you can find steps to
troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Generated by cloudfront (CloudFront) Request ID: HqMKiTQE3luCBWltMA3YOQeq5X-mCZ_xpemNH3KMXTD-5uiGT2SgpA== <

When I test this same request inside the automation rule (there is a validation test inside the Web request element) it works fine. 

Already checked the headers and authorization key and this is not the cause.

I think something in Jira Cloud is blocking my request for some weird reason.

Please help

[Mykenna Cepek]

Ensure you are not sending ANY body along with GET requests:

https://community.atlassian.com/forums/Atlassian-Platform-articles/Jira-Confluence-Cloud-APIs-return-403-Error-The-request-could/ba-p/2928153

[Bill Sheboy]

Hi @Juan Falguera -- Welcome to the Atlassian Community!

This is likely a timing problem, where the URL is evaluated / processed before the match() function completes.  I have seen the same symptom in the request body and with the Edit Work Item, advanced edit with JSON.

The mitigation for this is to first perform that match() to build the URL and save it in a created variable, and then use that variable in the Send Web Request action:

• action: create variable
  • variable name: varURL
  • smart value: your expression
• action: send web request
  • Web request URL: {{varURL}}
  • ...

Kind regards,
Bill

[Juan Falguera]

Hi @Bill Sheboy

Thank you for your answer. I tried to do the changes you suggested, but now I am getting this error:

<TITLE>ERROR: The request could not be satisfied</TITLE> 

<H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: QmWu-3x-rrrhE5EsQQevu4CK3mPuNROwZL5bZntsNCm-utboyYHG4Q==

I figured that sometimes the rule works, but most of the time not.

[Bill Sheboy]

First thing, yesterday Atlassian had an automation-impacting incident causing processing delays / errors.  That has since resolved, so are you still seeing the symptom today?  If so...

Please post an image of your complete rule (in a single image for continuity) and an image of the audit log details showing the rule execution (with all of the areas expanded).  Those will help provide more context.

Until we see those images...

Have you tried writing that variable {{varURL}} to the log to confirm it contains what you expected?

Can the content added to the URL contain characters which need to be escaped, such as by adding urlEncode()  to the values?

[Juan Falguera]

Hi. I opened a ticket for Jira support and they just replied. 

"Recently, we implemented changes to our REST APIs that block GET requests sent with a body. This includes any requests containing the value null."

Doing that solve the problem

Thanks again for your assistance.