Recurring events that stop generating correctly, or a listing showing the wrong occurrence as upcoming, usually points to the recurrence rule itself being misconfigured or a plugin update changing how recurring instances are calculated and displayed.
Check what the next few occurrences actually show against what you’d expect
Look at the next three or four occurrences of the recurring event and compare them against the pattern you actually intended (weekly, monthly, specific days). A pattern that’s subtly wrong from the start is easier to spot this way than by looking at just the next single occurrence.
Event listing & recurrence errors
A recurring event's occurrences fixed, whether the rule was wrong from the start or a plugin update broke it.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A recurring event isn’t generating occurrences correctly, or the listing shows the wrong one as next | This fix covers it |
| The issue is booking availability for the event, not the recurrence pattern itself | Booking calendar availability errors |
| You want ticketing or attendee data corrected, not the event listing itself | Ticketing & attendee data repair |
| You’re setting up a recurring event for the first time, not fixing an existing broken one | Still covered by this fix, treated as an initial setup rather than a repair |
What you are seeing
- Occurrences missing from the expected recurring pattern
- The listing showing an already-past event as the next upcoming one
- Recurrence stopping after a certain date without an intended end
- The issue possibly starting after a plugin update
Common causes
- The recurrence rule itself set up incorrectly from the start
- A plugin update changing how recurrence is calculated, breaking a previously correct pattern
- An end date or occurrence limit set unintentionally
- A caching issue serving a stale version of the event listing
- Two overlapping recurring rules on the same event conflicting when generating the same date
What we do
- Review the current recurrence configuration against the intended pattern
- Identify the specific misconfiguration or cause
- Correct the recurrence rule or resolve the caching issue
- Verify the next several occurrences generate correctly
- Check the listing displays the genuinely correct upcoming occurrence
- Confirm the pattern continues correctly going forward
What is included
- The recurrence issue identified and corrected
- Verified correct upcoming occurrences
- Confirmed accurate listing display
- The pre-fix backup, kept for 30 days
Not included
- Booking availability issues for the event, a separate, related fix
- Ticketing or attendee data repair, a separate, related fix
- Setting up a new recurring event pattern from scratch, if that’s genuinely your need instead
- Ongoing monitoring as future plugin updates occur
Questions about this fix
Why would a plugin update break a recurrence pattern that was already working?
Some plugins change how they calculate recurring instances internally between versions, which can alter behaviour for existing events even though nothing about your original configuration changed.
Will fixing this affect past occurrences that already happened?
No, this corrects future occurrence generation — past, completed events remain as they were.
Could caching really cause an event listing to show the wrong upcoming date?
Yes, if the listing page is cached and not refreshed after an occurrence passes, it can continue showing outdated information until the cache clears or is corrected.
How do I know if my recurrence rule was ever actually set up correctly?
We'd review the original configuration against your actual intended pattern, which sometimes reveals the rule was subtly wrong from the very beginning rather than having broken later.
Is this urgent if it's currently showing the wrong next event?
Worth prioritising if customers are seeing incorrect information about when an event actually occurs, since that can lead to real, avoidable confusion or missed attendance.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.