About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Hubspot New Ticket Property Change Trigger error: "The maximum allowed batch size is {} [100]"

  • 7 April 2023
  • 1 reply
  • 202 views
DCapture

I am having an issue specifically when I try to trigger a zap using the “Change to Ticket Property” in Hubspot.

When I try to use it it tells me that I have reached my secondly limit. Every other Zap that makes calls to Hubspot is working. This zap only runs a couple of times a week, so it definitely shouldn’t be exceeding the number of calls it can make to Hubspot.

I have tried testing it by having it only retrieve one other property to make sure that none of my Hubspot properties is making it freak out. Still doesn’t work. I am thinking it is just a glitch from a recent zapier updated. This zap has been functioning perfectly for months. This is a new and sudden issue.

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

ken.a
Userlevel 7
Badge +6

Hey there @DCapture,

It appears that you have already gotten in touch with one of our Support Specialists about this issue. Here is the response they provided:

It looks like this is related to an issue with the HubSpot integration. Other users have been experiencing this same error, and I have also found that there is an open bug report that documents this.
 
HubSpot seems to retrieve this error message when there are more than 100 tickets to be retrieved when you test the trigger step. 
 
Although I don't have a solution for you at this time, I have gone ahead and added you to the bug report as an affected user which adds more weight to the issue and ensures that you'll be notified once it's fixed.
 
I'm sorry, I wish I had a more immediate solution for you. We do notify the HubSpot team from our end, but a nudge from their users can sometimes carry more weight!

For any further inquiries about the bug, I recommend keeping in touch with our Support Specialists.

Thank you! 😊

 

Terms & Conditions