Zaps turning off immediately on page refresh - no error messages

Hey ​@monetize.academy,

Here is a helpful article about why a Zap can’t be turned on- https://help.zapier.com/hc/en-us/articles/8496199466125-Can-t-turn-on-or-publish-Zap

Referencing the common problems from the article-

• Zap has incomplete steps
• App accounts are not connected
• Connected app limitations
• Zapier account limitations
• Your draft is identical to the published Zap
• Your account restricts or prohibits the app
• Your account has publish approvals enabled
• Your Zap has a step that requires the Zap owner to publish

You may want to check if it’s identical to an already published Zap. Also make sure that you are the owner of the whop group. Hope it helps!

PS: If you need more active help, I’m happy to connect through my Zapier Solution Partner page if you’d like to reach out here- https://zapier.com/partnerdirectory/automation-jinn

If the Zap turns on, but turns back off right after refresh, and there is no run history, this usually means it is not a filter/path problem.
It is more likely a Zapier-side validation/app connection issue that is happening before the Zap can even start.

Simple things to check:

1. Make sure the trigger account is fully connected again
2. Try making a copy of the Zap and turn on the copy
3. Check if the Whop app version/connection is the real cause
4. Check Zapier Alerts / Apps page for hidden broken-auth or connection warnings

Since both Zaps do the same thing, with no error and no runs, I would say this looks more like a platform/app issue than a build issue. Zapier says Zaps can fail to stay on if there are incomplete steps or disconnected app accounts, and broken auth issues can also show up in Alerts.

So the best next step is to contact Zapier Support with the two Zap IDs, because this does not look like normal Zap behavior.

Hi ​@monetize.academy 

Help link to reference for why Zaps automatically turn OFF: 

Hi ​@monetize.academy 

Your Zaps are failing a "pre-flight" validation check on Zapier's servers. The silence (no error, no run history) means the issue occurs after you click "On" but before any trigger poll.

Most likely causes (in order):

1. Missing permission in Whop – The payment_succeeded trigger may require a paid plan or specific API scope. Verify your Whop account has webhook access enabled.

2. Corrupted Zap state – Make a copy of the Zap and try turning the copy on. This often resolves silent corruption.

3. Hidden auth warning – Check your Zapier Alerts page (dashboard → Alerts) for broken authentication that doesn't surface in the editor.

Quick diagnostic test:

Create a minimal Zap with only the Whop trigger (no filters, no Monday.com). Turn it on. If it stays on, add steps back one by one until you find the breaking point.

If none work: Contact Zapier Support with both Zap IDs (352712983 and 357536591) and state: "Zaps turn off after refresh with no error messages or run history." This bypasses generic troubleshooting.

Documentation: The official Zapier help article Can't turn on or publish Zap confirms that incomplete steps, disconnected accounts, and permission issues can prevent a Zap from staying on, even if no error message appears. The "copy the Zap" solution is also widely documented in community-resolved cases.

If you're still running into issues after trying these steps, feel free to drop a screenshot of the error and a quick description of what your Zap is doing—happy to take a look and help troubleshoot.

And if you'd rather just get it sorted quickly, I offer a free 20-min Zapier troubleshooting call. Book it under Resources on my Zapier Directory profile: https://zapier.com/partnerdirectory/automatemybiz!-->