Why did my Zap stop?
Short answer
Usually the connection was cut in Jounce, or the Zap was turned off. If Zapier is missing from Connected apps, reconnect Jounce inside Zapier, then turn a Zap that starts from Jounce off and on again.
Nothing in your audience changed when the Zap stopped. A stopped Zap adds, removes, and changes nothing. The Integrations page and the Zap’s own history on Zapier say which of these it is.
Zapier is missing from Connected apps
Jounce cut Zapier off, for one of two reasons:
- An Admin or a Manager disconnected it.
- The person who connected it left the workspace, was removed, or became an Editor. Their connection ended with their access.
A Zap that starts from Jounce gets nothing to run on, since Jounce stops telling it what happens. A Zap that adds or changes people in Jounce stops the next time it tries to run. Zapier asks you to reconnect the account, and may call the connection expired.
An Admin or a Manager reconnects it. Open the Zap, choose its Jounce step, connect a Jounce account, and approve it again; see Connect Jounce to Zapier. A Zap that adds or changes people in Jounce runs again after that.
A Zap that starts from Jounce needs one more step: turn it off, then on again, in Zapier. Zapier signs up for events from Jounce only when a Zap turns on.
The Zap is turned off
Jounce stops telling a Zap that’s off. Turn it back on and Jounce starts again from that moment; what happened while it was off isn’t sent later.
The event happened, but the Zap didn’t run
- Subscriber Created doesn’t fire for a CSV import. It also doesn’t fire when someone already in your audience is updated.
- If a Subscriber Added to Segment Zap has a segment picked, it runs only for that segment.
- Opens, clicks, bounces, and complaints never start a Zap. They aren’t triggers.
The Zap ran, and Jounce refused
The run’s details in Zapier show Jounce’s own sentence; see Why didn’t my Zap add someone to Jounce?
It reaches the wrong workspace
The connection reaches the workspace you were in when you approved it. Switch to the right workspace, then connect a Jounce account again in the Zap; see Switch workspaces.
It runs slower than usual
Jounce accepts a steady number of requests from connected apps. When a Zap sends more than that at once, Jounce asks it to wait, and Zapier tries again by itself. Nothing is lost.
More in this topic
Updated