Polling for issues to show sample issues, or perform the Created Request / Updated Request triggers sometimes fails if the issues are large

Issue Summary

The Jira Service Desk for Zapier app (maintained by the JSD Ecosystem team) polls the Jira issue search API to fetch issues to show Zapier users as samples.

This search also powers the Created Request and Updated Request triggers.

Because we fetch 100 issues at a time, if the issues are larger (and the combined response is > 6MB in size), Zapier fails to process the response.

Steps to Reproduce

1. Create an account in Zapier
2. Set up a rule with an Updated Request trigger
3. Connect to a Jira site with at least 100 issues with a lot of data (attachments, fields, comments, change history, etc.) . such that the issue search returns > 6MB of data.

Expected Results

The samples are displayed to the user.

Actual Results

The user sees an error that the "body size is too long" and cannot continue to set up the rule with sample data.

Alternatively, if this were to happen when polling issues to trigger a rule the rule would fail to trigger and the user would be alerted by email.

Workaround

Currently there is no workaround.