Send Web Request action should not deem all 40x responses as problematic

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Actions
    • 0

      I'm using Automation For Jira to GET from an external API. 

      If this particular API responds with a 404, that tells me a resource does not (yet) exist, rather than something fatal having occurred.

      Simply ceasing the automation workflow at the point a non-200 response is received is not always desirable. 

      The ability to toggle whether the Web Request action stops or continues after a non-200 response would be most helpful here.

       

      Cheers!

       

            Assignee:
            Unassigned
            Reporter:
            Mike Kenyon
            Votes:
            25 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: