Your tasks, on time. And you set nothing up.

What it does, in one sentence

It gives WordPress a queue of its own and connects the site to the Faro scheduler, so tasks run when they are due instead of when somebody visits.

WP-Cron is not cron: it is a visit-driven trigger. This plugin does not patch it, it goes around it. The queue lives in your database (wp_faro_sch_tareas): each task has its due time, its interval, its attempts and an idempotency key. The Faro service runs them, signing every call with your site key. You install the plugin and press “Connect”; the rest is on us.

Why WP-Cron falls behind

It is not a configuration mistake: these are six core behaviours that show up exactly when the task matters.

• It only runs what is due, when there is a visit: on a low-traffic site a 9:00 task may run at 14:00, or never.
• DISABLE_WP_CRON turns it off entirely: the usual production advice, and it leaves tasks with no trigger at all.
• One global 60-second lock: if a task hangs, everything else waits behind it.
• Long jobs die on max_execution_time or the FastCGI timeout, halfway and without a word.
• The loopback call can be blocked: many hosts and firewalls cut the request a site makes to its own wp-cron.php.
• An external heartbeat is blind: it knows the site answered 200, but not what ran, whether it failed or how long it took.

How it works, step by step

1. You queue the task from the panel, WP-CLI or the signed API: action, data, when, and optionally how often.
2. The Faro service signs and calls your site every 30 seconds, with HMAC-SHA256 over “timestamp.body” and a five-minute window to stop replays.
3. The site claims one row: UPDATE … WHERE estado='pendiente' AND proxima_vez<=ahora. Two processes cannot take the same task.
4. It runs registered actions only: if the hook does not exist, the task fails and says so instead of pretending.
5. It records the result: duration, state and error in wp_faro_sch_ejecuciones, which feeds the charts.
6. It retries with growing backoff (60, 120, 240, 480 s) and, once attempts run out, leaves the task dead without blocking the rest.

A panel that tells the truth

Five screens, no noise: connection health, tasks by state, runs per hour and per day, a filterable queue and settings.

• Overview: whether the service is calling, when it last did, tasks by state and two charts (24 hours and 7 days).
• Queue: state filters and search by action or key, with each task error in plain sight, plus run, retry and delete.
• New task: action, JSON data, due time, interval and idempotency key.
• Settings: tasks per request, retention, attempts, lease time and the Faro connection card.
• Help: what it does, what it does not do, and the exact header contract.

Connecting: one click and nothing else

No server to rent, no Raspberry Pi to buy, no hosting cron to touch. The scheduler runs on the Faro service.

1. Install the plugin, like any other.
2. Go to Settings → Faro connection and press Connect.
3. Done. Within a minute your site shows as connected and starts receiving calls every 30 seconds.

The only thing sent is your site's public address and the signing key the plugin generates. Not your content, not your users, not your database. You can disconnect at any time from the same card, and the key can be regenerated whenever you want.

Prefer to run the scheduler yourself? The plugin still ships the advanced mode: push URL and secret, no service involved.

How it looks

Free, and Pro when you need it

The plugin and the service connection are free. What you pay for is what takes more work on our side.

What it does not do

• It does not guarantee execution if your site is down or the service cannot reach it: it queues and retries, it does not perform miracles.
• It does not replace WP-Cron: it coexists with it, which can stay as a third safety net.
• It does not run arbitrary code or paths: only actions already registered in your WordPress.
• It does not touch your content: the service only receives each task response.
• It does not prevent overlapping runs if you point two schedulers at the site at once.

Privacy: your site makes no outbound requests. All traffic is inbound and signed.

Download

FWP Scheduler 0.2.3 (free, GPL)

Install it from Plugins → Add New → Upload Plugin.

Requirements

• WordPress 6.4 or later (tested up to 7.1).
• PHP 7.4 or later.
• HTTPS to the site so the signature never travels in clear text.
• Your site must be able to receive the service call: no outbound ports to open.

Package fingerprint (SHA-256): 2847593450ed199c1470eaa6f8ba80b02099b7ea51c02aebd188bf23b90ecdf1