Short answer

First, check it has actually stopped rather than just looking like it has. A recurring task only shows a rolling window of upcoming occurrences (about the next 12 for weekly, 20 for daily), so the list appearing to "stop at a date" a few months out is normal — it tops itself up automatically (see how far ahead are recurring tasks created).

If new occurrences have genuinely stopped appearing, the usual cause is that an end date has been set on the recurrence. An end date tells Civic.ly to stop creating new occurrences after that day. Open the routine (or recurring inspection/job), check the recurrence end date field, clear it, and choose Update → all future occurrences. Leaving the end date blank keeps it running indefinitely. Nothing already done is lost — completed occurrences stay on the record.

Detail

This applies to any recurring item, not just routines — a standalone recurring inspection or job has the same recurrence end-date field as a routine does.

An end date can end up set a few ways: deliberately for a temporary or seasonal schedule (see when to set a recurrence end date), or accidentally — for example while editing the recurrence, or by using a "stop / delete from this point forward" option. The symptom is the same: the item generates its occurrences up to the end date and then produces no more, so the work quietly drops off the schedule a week or two later.

A worked example: a council set up weekly inspections for nine play areas, but an end date a few days out had been applied to eight of them. Those eight ran for the first week or two and then stopped, while the ninth (which had no end date) kept going — so on the ground it looked like "only one of my play areas still shows up." Clearing the end dates and letting the schedule rebuild brought all nine back.

To fix it:

  1. Open the routine or recurring task.
  2. Look at the recurrence end date — if there's a date in it that you didn't intend, clear it (or move it to when you actually want it to stop).
  3. Save with Update → apply to all future occurrences.
  4. Check over the next few days that upcoming occurrences are reappearing. If they don't come back on their own, contact support and we'll rebuild the schedule for you.

Watch-outs

  • Leave the end date blank by default — that's what keeps a recurrence running. Only set one for genuinely time-bounded or seasonal work.
  • "It stops at July" on its own is usually fine — that's the rolling window, not a stopped recurrence. The tell that something's actually wrong is occurrences not topping up and no new ones being created as time passes.
  • Ending one occurrence vs ending the series — a "delete from this point forward" action ends the whole series from that date, not just the one task. Use it deliberately.
  • Completed work is safe — clearing an end date or rebuilding the schedule doesn't remove inspections your team has already done.