Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Project Automation Web Request comment when failing

Currently we are using Project Automation to send a web request. Based on the response code of the webhook we are commenting on the ticket (if 200 comment success else comment failure). This seems to work great unless we get a 401, 500 etc error code. 


When a 500 or 401 error is thrown the rule errors out in the web request step and never hits the if/else steps.


Is there a way to comment to a ticket when the the web request set fails?

1 answer

0 votes
Yvan Martin Atlassian Team Sep 29, 2020

Hi Michael,

Developer from Automation here.

Currently our web request action does not currently support continuing after receiving an error status (non-200 request code), and will result in an error in your rule.

In the future we hope to add an option to continue running and allow you to branch on the status like you mentioned, we have an existing improvement item, but it isn't been prioritised at this time: 


@Yvan Martin This is a serious issue for us because the send-web-request automation is basically broken at this point:
* the connection is considered to be always kept open; if a second message comes after the connection was closed, the request is considered failed (with a 500 response code) because the connection is considered unavailable instead of a new connection being opened
* we cannot put in a retry because the step closes the execution at the point of receiving this error

This is not a usable automation tool.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

174 views 3 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you