Features · Protect revenue
Find the renewals that failed while you slept.
A renewal batch that fails at 3 am looks like nothing in the morning: the site is up and new orders are coming in. Operanse watches renewals as their own series, learns when this store renews, and tells you when that changes.
On every plan, Watch (free) includedWatch: a fixed check for failing renewals. Monitor: the store’s own normal, hour by hour.
First attempts, Sat 02:00–05:00
Retries of those 14, counted apart
Renewals fail quietly, and some never run at all
Renewals run in the background, usually overnight. A gateway problem fails a batch; a stalled queue stops renewals altogether, and then nothing fails at all: they just do not happen. Either way the checkout looks healthy, so nobody looks.
- A night of failed renewals inside a normal-looking day.
- A retry run that makes one bad night look like two.
- A renewal day with no renewals, and no error anywhere.
What you can see
First attempts decide the failure rate
A card that declines and then succeeds on the retry the next day is one failure, not two, and the retry is counted on its own. So a spike in retries after a bad night does not look like a second bad night, and what is still failing stays visible.
≈ $890 of renewals at risk; retries counted apart
Renewals that never run
Renewals are scheduled actions. When the queue that runs them stops, the renewal count drops to zero on a day this store normally renews, and that is reported as stopped. The queue behind it is watched too, so the incident says why.
renewals, Sun 02:00–05:00
scheduled actions
Judged against this store’s renewal cycle
A store that renews on one day of the week is compared with its other renewal days, not with a Tuesday. The dashboard reads the renewal schedule from WooCommerce Subscriptions and says the date its normal will be ready.
- renewal pattern
- weekly, mostly Saturday night
- baseline
- learning: needs two Saturdays
- until then
- fixed rules, each alert naming the threshold it used
An incident with the orders, and an answer you can ask for
The incident counts first attempts and retries apart and carries an estimate of the money affected.
- first attempts
- 14 failed, 02:00–05:00
- usual
- 1–3 for this store’s Saturday renewals
- retries
- counted apart
estimate ≈ $890 of renewals at risk
Likely cause: the background queue that runs renewals stalled, not the payment gateway. WP-Cron missed a run at 02:08, and from 02:10 to 03:35 no scheduled action completed while 14 renewals failed. Calls to the gateway answered normally throughout, and the failures stop the minute the queue resumes.
11 of the 14 went through on the 05:00 retry; 3 are still failed and are listed in the incident.
Source: cached telemetry, fresh as of 2 minutes ago · incident inc_01J9… · read-only.
Coverage and limits
What it covers
- Failed renewals. Renewals attempted, succeeded and failed, from WooCommerce Subscriptions as each one runs; first attempts decide the failure rate.All plans
- Renewals that never run. A renewal count that drops to zero on a day this store normally renews, and the scheduled actions behind it.Monitor
- The renewal cycle. A daily rhythm learned in 48 hours; a weekly renewal day seen twice, over two weeks.Monitor
Limits
- It reads WooCommerce Subscriptions. Renewals run by another subscription plugin are not counted as renewals.
- It does not retry a renewal, change a subscription or contact a customer. It is read-only.
- Revenue at risk is an estimate from the store’s own history.
How long the renewal baseline takes
Most stores renew in a daily rhythm, and their normal is learned in 48 hours. A store whose renewals bunch up on one day of the week needs to see that day twice, so its renewal baseline takes two weeks. The dashboard reads the renewal schedule from WooCommerce Subscriptions to know which kind of store it is, and says the date the baseline will be ready.
Until then, fixed rules apply, and every alert they raise says which threshold it used.
What a failed renewal costs (calculator) · Stripe reason codes for renewals
Start using it
- Install the plugin from wordpress.org. It is read-only: it cannot change the site.
- Pair the site with the token from your dashboard. Setup, step by step
- Fixed checks start at once. The learned renewal normal is ready in 48 hours for a daily rhythm, two weeks for a weekly one.
All plans On every plan, Watch (free) included. Watch: a fixed check for failing renewals. Monitor: the store’s own normal, hour by hour. Compare plans
Questions
What does the free plan check?
Watch checks for failing renewals with a fixed rule and emails a critical alert. Monitor learns the store’s own renewal normal, hour by hour, spots renewals that never ran and prices each incident. Insight adds an AI review of the likely cause.
Why are retries counted separately?
So one bad night counts once. Retries are counted on their own, so a retry run neither inflates the failure rate nor hides what is still failing.
Can it fix the failed renewals?
No. It names what failed and what is still failing. Retrying, updating payment details or contacting customers stays with you.