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?
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: https://codebarrel.atlassian.net/browse/AUT-521
Thanks.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.