Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Getting 408 Error When Sending Web Request to Adobe Workfront

Patrick Cook
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 24, 2024

Hello,

We're trying to setup some automations with our service desk, and with that we're trying to send a web request. When sending this web request, we mainly get a 408 error (NoHttpResponseException: The target server failed to respond), though I have seen a (I think) 422 sock error. With that in mind, we reached out to our Workfront support team with this issue. 

For context, I sent a request from Jira and then I sent the same exact request (with the same headers) from my computer using Postman and also from Power Automate in our Microsoft 365 tenant. My computer and Power Automate were successful, but Jira was not.

When looking at the logs, they saw our successful requests from my computer and Power Automate, but didn't see any trace of Jira, not even a block.

Is there a default restriction perhaps or maybe somewhere we need to allow certain URLs/IPs for outbound web requests?

Here's our request: https://hidden.my.workfront.com/attask/api/v17.0/proj?name={{issue.properties."proforma.forms.i1".state.answers.64.text.urlEncode}}+%28{{issue.properties."proforma.forms.i1".state.answers.19.choices.urlEncode}}+Rooftops%29+%7C+New+Client+Setup+%7C+Starts+{{issue.properties."proforma.forms.i1".state.answers.59.date.urlEncode}}&templateID=hidden&portfolioID=hidden&companyID=hidden&ownerID=hidden&groupID=hidden&status=CUR

I did verify that the smart values do work and are sending correct values in the validation portion of the automation.

Thanks!

1 answer

1 accepted

0 votes
Answer accepted
Patrick Cook
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 26, 2024

Posting the answer back here in case anyone else gets stuck. Jira Automation doesn't like path parameters in POST requests, so any path parameters must be passed to the body. Make sure to add a header "Content-Type = application/x-www-form-urlencoded" and copy-paste any path parameters you have in a custom data body form. (and be sure to remove the question mark)

So in my case, the URL will be "https://hidden.my.workfront.com/attask/api/v17.0/proj" and the custom body will be "name={{issue.properties."proforma.forms.i1".state.answers.64.text.urlEncode}}+%28{{issue.properties."proforma.forms.i1".state.answers.19.choices.urlEncode}}+Rooftops%29+%7C+New+Client+Setup+%7C+Starts+{{issue.properties."proforma.forms.i1".state.answers.59.date.urlEncode}}&templateID=hidden&portfolioID=hidden&companyID=hidden&ownerID=hidden&groupID=hidden&status=CUR"

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events