Skip to main content
Best answer

API call rate has been exceeded


HI There,

We are have a WordPress Site that’s using the Gravity Forms to GoToWebinar Zap connection

We have a webinar that has just gon live and have several Sign ups trying to connect

 

Unfortunately the following error is happening for all Attempts to connect between the 2 Applications

 

"The API call rate has been exceeded for the minute.". This usually happens because there is a limit to the number of times we can send information to an app or service within a period of time. Please wait for your limit to be reset and try again.

 

 

Hi Everyone!

 

We came across an odd error this morning and wanted to ask your opinion...


We have not seen this error before so we are not sure how best to proceed with trouble shooting it?
The Data seems to be working fine getting into the system from the Gravity Forms end but 
It appears that error happens when it hits the GoToWebinar connection.

 

We have checked in GoToWebinarand it does indeed appear that all of the Data is eventually getting into GoToWebinar which is Great!!!

We are just worried about this error and wondering if there is anything we need to do to make sure the whole process runs smoothly again

Any Advice or Guidance would be greatly appreciated

Kind Regards

Best answer by jesseBest answer by jesse

Hey friends! For anyone following this thread, we wanted to let folks know that this was a bug that has since been resolved.

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

nicksimard
Forum|alt.badge.img+11
  • Zapier Staff
  • 2115 replies
  • April 6, 2020

Hi there!

It looks like you’ve got a conversation going on with our Support team and they’re digging into that for you. So sorry you’re being affected by that GoToWebinar bug!


jesse
Forum|alt.badge.img+9
  • Architect
  • 1348 replies
  • Answer
  • June 10, 2020

Hey friends! For anyone following this thread, we wanted to let folks know that this was a bug that has since been resolved.