Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-906

Calling an "incoming webhook" trigger with a payload greater than ~1MB doesn't execute but returns 200 OK

    • Minor
    • Jira Software

      Issue Summary

      Payloads over 1MB do not trigger the incoming webhook trigger, however still return a 200 OK response.

      Steps to Reproduce

      1. Create an automation rule in Jira Cloud with "Incoming webhook" trigger and "Log action".
      2. Send a POST request to the webhook with the attached test_OK.json as body.
      3. The response is HTTP 200 and the Audit log reflects that the trigger is invoked. :check_mark:
      4. Send a POST request to the webhook with the attached test_NOT_OK.json as body.
      5. The response is HTTP 200, however the trigger is not getting invoked according to the Audit log. No error is displayed. :cross_mark:

      test_OK.json

      test_NOT_OK.json

      Expected Results

      The appropriate HTTP error code.

      Actual Results

      The execution does not get triggered, but the response from the request is 200 OK.

      Workaround

      None really, ensure payloads are less than the limit.

        1. test_NOT_OK.json
          1.32 MB
          Liam Tan
        2. test_OK.json
          1.32 MB
          Liam Tan

          Form Name

            [AUTO-906] Calling an "incoming webhook" trigger with a payload greater than ~1MB doesn't execute but returns 200 OK

            Dario B made changes -
            Description Original: h3. Issue Summary



            Payloads over 1MB do not trigger the incoming webhook trigger, however still return a 200 OK response.
            h3. Steps to Reproduce
             # Create an automation rule in Jira Cloud with "Incoming webhook" trigger and "Log action".

             # Send a POST request to the webhook with the attached test_OK.json as body.

             # The response is HTTP 200 and the Audit log reflects that the trigger is invoked. :check_mark:

             # Send a POST request to the webhook with the attached test_NOT_OK.json as body.

             # The response is HTTP 200, however the trigger is not getting invoked according to the Audit log. No error is displayed. :cross_mark:

            [^test_OK.json]

            [^test_NOT_OK.json]
            h3. Expected Results

            The appropriate HTTP error code.
            h3. Actual Results

            The execution does not get triggered, but the response from the request is 200 OK.
            h3. Workaround



            None really, ensure payloads are less than the limit.
            New: h3. Issue Summary



            Payloads over 1MB do not trigger the incoming webhook trigger, however still return a 200 OK response.
            h3. Steps to Reproduce
             # Create an automation rule in Jira Cloud with "Incoming webhook" trigger and "Log action".
             # Send a POST request to the webhook with the attached test_OK.json as body.
             # The response is HTTP 200 and the Audit log reflects that the trigger is invoked. :check_mark:
             # Send a POST request to the webhook with the attached test_NOT_OK.json as body.
             # The response is HTTP 200, however the trigger is not getting invoked according to the Audit log. No error is displayed. :cross_mark:

            [^test_OK.json]

            [^test_NOT_OK.json]
            h3. Expected Results

            The appropriate HTTP error code.
            h3. Actual Results

            The execution does not get triggered, but the response from the request is 200 OK.
            h3. Workaround



            None really, ensure payloads are less than the limit.
            Dario B made changes -
            Labels New: ecohelp
            Liam Tan made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Liam Tan created issue -

              Unassigned Unassigned
              7d749258828e Liam Tan
              Affected customers:
              9 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated: