Skip to main content

I have multiple Zaps that integrate JotForms with Trello. These were working as expected a week ago. Then, I started getting multiple “502 Server Error” emails, which I have gotten in the past when Trello/JotForm have been down temporarily. However, I’ve been getting them every day for the past 5 days or so, but I didn’t see any failed Zaps. Then, this morning, I received a new error email with this message: “Trigger partner failure: ('Jotform throttling https://zapier.api.jotform.com/form/90435131864152/submissions?orderby=created_at%2CDESC&limit=100', 60)”

 

I went into the Zaps and it said I needed to reconnect my JotForm account, which I did (no changes have been made to my JotForm account or Zapier account). After I reconnected my account, I went to the next step to make sure it was working properly. However, now I am getting the error below when trying to select a form as a trigger:

 

 

Any recommendations for this? Like I said, we have not made any changes to our account as far as I’m aware. 

@User Services what is the status on this issue? It’s been several days now and several hundred affected users.


@User Services I am having the same issue with receiving repeated error messages for Jotform throttling. Can you please add me to the list of accounts that need resolution. Thank you.


@User Services Please add me to the list of accounts affected.


You can add me to the list as well.  Same problems.  Thanks.


Please add me to the list of affected users, so I can be notified of Jotform’s resolution. I’ve been getting the same error message daily. But nothing appears to be wrong on my end.


Hey friends - thanks for letting us know! I’ve added everyone who’s commented up to this point to the bug report. This ensures you’ll be emailed once a fix is in place.

In terms of an update, in the interest of full transparency, the Jotform app is owned and maintained by Jotform. We’re happy to continue tracking impacted users but aren’t able to advise on an ETA since that is dependent on their team.

I wish I had better news to share but rest assured, once news is available we’ll share that here! Thanks as always for your patience!


Same issue here. Please add me to the list.


We are having the same issue, please add me to the list


Hey! I’m having the same error as well. If you could add me to the list that would be great. 


Trigger partner failure: The app returned "500 Internal Server Error".

Now it’s a ‘500” error. We getting any closer to a resolution here? It’s been a week. :/


Hello, we’ve been having the same issue as well, please add us to the list. Thank you


Hey there, thanks for letting us know! I’ve got everyone added to that bug report. 


Hey all! I wanted to keep ya’ll in the loop that a potential fix was pushed by Jotform a few days ago and we’re currently monitoring. 

Hopefully I’ll be back again soon letting ya’ll know this is officially closed -🤞🏽.


I’m still receiving a mix of 502 and 500 errors, although, throttling is less happening now and the number of emails I’m receiving regarding errors is far less now.


I turned back on the Zaps that were causing the original issue in this thread (i.e. throttling errors).
I am now receiving these errors instead:

  • Trigger partner failure: The app returned "500 Internal Server Error"
  • Trigger partner failure: The app returned "502 Server Error"

On the positive side, I have stopped getting the “throttling” error message. On the negative side, I continue to get this error: Trigger partner failure: The app returned "502 Server Error". Is this error being addressed in your investigation/fix?

 

Jotform (1.3.2)

Trigger partner failure: The app returned "502 Server Error"


Hey ya’ll - thanks for sharing this! I’m back again for a quick update before we head into the weekend.

Our team is still working with Jotform on a solution. As you noticed, we’re still seeing quite a few errors. 😔 We’ll continue to keep everyone in the loop here and you’ll also receive an email when this is officially closed.

Thanks again for hanging in there with us. We understand the impact this has for everyone and we appreciate everyones ongoing patience!


I have a similar problem with : This auth is expired, Please reconnect here.

 

If I try with new account it tells me to connect to another jotform account but connecting to a jotform account with Gmail doesn’t seem to work.


Hey ya’ll - thanks for sharing this! I’m back again for a quick update before we head into the weekend.

Our team is still working with Jotform on a solution. As you noticed, we’re still seeing quite a few errors. 😔 We’ll continue to keep everyone in the loop here and you’ll also receive an email when this is officially closed.

Thanks again for hanging in there with us. We understand the impact this has for everyone and we appreciate everyones ongoing patience!

 

Jotform replied to my original support request saying they had a new version of the Zapier App which was “instant”. I edited all my zaps to use the new version of the app and so far everything is working without error as fa as I can tell, and it’s in fact a lot faster about transfering the data to my CRM that the old app.

 

Sorry that you have faced issues with your Zapier integration.

We have released a new Zapier "New Submission" instant trigger. Updating your zaps with this new trigger will eliminate the issues you are facing. 

 

Perhaps this will help others still having issues?


Ah, that’s super helpful to know! Thanks so much for sharing this here, @LifetimeBuildingSupply!


A huge *** Thank You *** to LifetimeBuildingSupply for sharing the above post!!!

 

I wanted to share the following instructions in case anybody was not entirely clear regarding LifetimeBuildingSupply’s suggestion about updating the Jotform app in your Zaps.

 

To update your Zaps to the “new version” of the JotForm app:

 

  1. View Zap.
  2. Edit Zap.
  3. In the Trigger block, expand the App & Event section.
  4. Click the Change button in the app field (see screenshot below).
  5. When the Change Trigger window appears, search and select Jotform.
  6. In the Event field, select “New Submission Instant” (see screenshot below)

 

After you do this, work your way through the remaining fields in the Trigger & Action Blocks of your Zap.  More than likely, you’ll need to “re-map” some (if not all) of your fields.  (In my case, all of my fields needed to be re-mapped.  It appears that the verbiage in the Jotform fields changed slightly.  For example, my “old” Jotform field said “Fields Parents Email”; the “new” Jotform field says “Answers Parents Email.”  See screenshot below for clarification.)

 

 

Now that I’ve made this change to all of my Zaps, I’ll report back if I continue to have any problems!


A huge *** Thank You *** to LifetimeBuildingSupply for sharing the above post!!!

 

 

Awesome tutorial on how to update! Exactly what i had to do and so far i have been using the new trigger this week and have not had any more issues. 


This makes me so happy to hear and really appreciate ya’ll coming back to share this with others! 🎉

While the bug is still open, I did share with the team this appears to be working for a few of you!


@christina.d - Please add my email/account as one of the accounts affected too.

While we plan on making the changes suggested above (using the Instant Jotform New Submission trigger)


Thanks, @Steve Chon - you’ve been added! 

Let us know how the new trigger works for you!