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.

Best answer

Why does Podio disconnect from Zapier?

  • 15 December 2021
  • 4 replies
  • 46 views
T

I have set up a flow in zapier.

It is a link in an E-mail ( this link is a link to a google form) 

When a person fills the form (Email and a workspace-name) it generates an action in Podio. It create a message in a certain workspace, that tells the members of that workspace, to let the person in to the desired workspace.

It works perfectly fine. My problem is, that it only works for a period, and then an error occurs

How can that be?

icon

Best answer by SamB 15 February 2022, 12:48

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

4 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @Tolkevaerket 

Check the Zap > Details > Change History for why the Zap auto turns OFF.

  • Off: Zaps that are turned off do not actively check for new data or perform actions. Zapier automatically turns your Zaps off for you in three situations:
    • You lose access to a paid feature the Zap uses (e.g., multi-step Zaps or premium apps) due to a trial expiration or plan downgrade.
    • Multiple errors occur each time the Zap tries to run. An email notification will be sent if a Zap is turned off due to errors.
    • You make a change to a trigger or action of the Zap. You will need to turn the Zap back on once you are done editing it.

 

You can open a ticket with Zapier Support for further troubleshooting: https://zapier.com/app/get-help

 

"An existing active hook is already present for this client" Error

This can happen if Zapier gets out of sync with your Podio application, you can fix it by deleting the active hooks.

First step - pause all Podio triggers in Zapier.

Second step - go to Podio developer tab for your app:

Final step - click delete on any remaining hooks:

 
⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
T

Hi Troy

Thank you very much for your answer.

when my Zap turns off, I go to history and turns it on again, but I can’t figure out why it turns off. You write 3 reasons in your answer.

I do not change anything, so option nr 3 is not the reason.

I don’t thing multiple errors occur each tine the zap tries to run. The Zap works perfectly for a period, and then suddently turns off. I don’t touch Zap, podio og google at all.

The option may be a reason.. I run on a free plan. Is that a problem?

 

Kind regard Henriette

Troy Tessalone
Userlevel 7
Badge +14

@Tolkevaerket 

Best to open a ticket with Zapier Support for further troubleshooting: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
SamB
Rank
Userlevel 7
Badge +11

Just wanted to follow up here to confirm that @Tolkevaerket did also reach out to our Support team about this. Support identified that the reason they were seeing these errors occurring was due to a known bug and added them to the list of affected users. 

We don’t have any workarounds to suggest or an ETA on when this will be resolved but we’ll be in touch by email as soon as it is. :relaxed:

Terms & Conditions