Workflow post-functions created via third-party apps (e.g., JWME) fail to execute due to webhook payload size limits.

XMLWordPrintable

    • 1
    • Minor

      Issue Summary

      Some post-functions created via third-party apps (such as JWME) are not getting triggered following a workflow transition.

      Backend logs indicate that the webhook fails to publish successfully because the payload size exceeds the maximum allowed limit (256KiB). Consequently, no transition events are registered or visible on the app provider's side.

      Steps to Reproduce

      1. Configure a shared action or post-function within a third-party app (e.g., JWME).
      1. Add this action as a post-function to a specific workflow transition.
      1. Trigger and successfully complete the workflow transition on an issue.
      1. Review the third-party app's execution logs.

      Expected Results

      The workflow transition completes successfully, the webhook triggers, and the selected post-function operation executes as intended.

      Actual Results

      The workflow transition completes without any UI errors, but the post-function fails to run.

      • App Logs: No events or invocations are displayed.
      • Backend Logs: Webhook publication fails with an error indicating that the payload size exceeds the allowed threshold.

      Workaround

      To mitigate this issue, coordinate with your app support team or adjust configurations to reduce the webhook payload size by:

      • Limiting the number of custom fields included in the payload.
      • Implementing filtered webhooks to send only essential data.

              Assignee:
              Rampreeth Ethiraj
              Reporter:
              Abhishek Singh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: