Hi there @Andrés O,
Welcome to the Community! 🎉
Upon investigation, it appears that you have already contacted one of our Support Specialists and the error you are encountering is a known bug within the Jira Service Management “Updated Request” trigger. Here’s what they said:
I understand that you cannot turn on your Zap with the Jira service management trigger. I checked the logs and noticed this error is preventing the Zap from getting turned on.
message
Failed to read_poll during SamplePoll: Response payload size exceeded maximum allowed payload size (6291556 bytes).
I dug into this and saw that a few other users had encountered this problem. As it turns out, you've run into a known bug, unfortunately.
We already have a bug report in place, so I've added your contact information to the ticket. There isn't a workaround, but we'll get back to you immediately when a fix ships.
Sorry about hitting a dead end here. Although the ticket may show "Solved," this only refers to the ticket’s status. We'll notify you via email when the bug is fixed.
We regret to inform you that there is currently no workaround available for this issue, and we cannot provide much information on why this bug is occurring. However, we have added your email address to the open bug report. This action will bring the issue to the attention of our integration developers, help track and prioritize fixes, and enable us to notify you via email when the issue is resolved.
We understand that you may be concerned about the timeframe for resolution, but unfortunately, we do not have an estimated time of arrival (ETA) for the fix. Rest assured, we have added you to the list of users affected by this issue so that we can inform you as soon as there are any updates.
Thank you for understanding!