All of a sudden, a particular Zap is not getting triggered from my Glideapp

Hello good people,

I’m experiencing a strange behavior in my Glide App. A particular button triggers a zap and it worked fine until past two hours. All of a sudden I don’t see any action in my Zap history, I did not make any big change in my zap too.

My success message shows up in Trigger zap step. Just to make sure I didn’t overshoot any quota I created another simple zap that sends out an email with To, Subject and Body hard coded, it worked.

Has anyone faced anything similar?

So it’s a problem with that specific Zap, and not any other Zaps?

1 Like

Yeah, to make sure it’s with a particular zap, I created a new zap with a simple step and it fires. But this one which was working already never gets hit from yesterday. Probably I shall duplicate that zap to a new one and see. No error message from zap too.

The simple zap that was firing yesterday stopped working now. The only difference is, I copied my Glideapp to another workspace, selected a copy of data and I reconnected to Zapier using this new app’s Zapier API Key. I’m able to see the two zaps that are connected using the new API Key. But when I see the zap history, they are not run at all. The success message of that particular trigger in Glide shows up though.

I would suggest trying to create a webhook as the first step of your Zap, and trigger that webhook instead to see if it’s the problem.

It also allows you to send more fields.

1 Like

@ThinhDinh Trigger webhooks suggestion was of great help. It worked like a charm, in fact, it helped me solve the problem of sending personalized emails to multiple recipients in 1 click of a button. A long thread was open for this and now I can close that too !

Thank you so much !

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.