Troubleshooting

Almost every "it did not run" has one of a handful of causes. In rough order of how often they turn out to be the answer:

The automation is not live

Zapify → Automations shows the status of each one. Click the status to change it. A Draft automation has never been published; an Off one was paused deliberately.

A trigger or an action is switched off

Separate from the automation's own status. Each trigger and action carries its own switch — Live, Off, or Draft — shown on its card.

This is the one people miss, because the automation looks perfectly live. An action switched off is skipped and the rest of the run carries on.

Pausing an automation does not switch its steps off, and resuming does not switch them on. That is deliberate: an action you turned off stays off.

A condition was never finished

A condition row with nothing to compare stops everything. Zapify refuses to set an automation live while one exists, but an automation that was already live before the condition was added can end up in this state.

The card says so directly: "3 conditions are unfinished, so this never runs", in amber. Open the filter and either complete the rows or remove them.

The trigger filter did not match

A trigger filter that does not match records nothing at all — no run, no log entry. That is by design, but it does mean "nothing in the log" is a symptom rather than a dead end.

Set Zapify → Settings → Log verbosity to Verbose and try again. Misses are recorded at that level, with both sides of the comparison and their types.

The per-user limit is reached

Times per user on the automation defaults to 1, which means each person triggers it once ever. Set it to 0 for no limit.

The queue is not running

Delayed and queued actions depend on WP-Cron. On a site with no traffic, WP-Cron does not run, so nothing in the queue does either.

Zapify → Settings → System status reports whether Action Scheduler has a backlog and whether WP-Cron is disabled without a real cron replacing it.

The host plugin is missing

An automation that uses WooCommerce stops working if WooCommerce is deactivated. Zapify marks it inactive with a stated reason rather than failing silently, and nothing is deleted — reactivate the plugin and it works again, configured exactly as it was.

Reading a failed run

Zapify → Logs, then open the run. Each action shows the configuration it was called with after tokens were resolved, recorded before it executed. If a token resolved to nothing, you can see that it did.