Short answer

Civic.ly doesn't create every future occurrence of a recurring task at once — it keeps a rolling window of upcoming ones and tops it up automatically. As a rule of thumb it holds roughly the next 12 cycles for a weekly routine and the next 20 for a daily one (monthly is about 12 cycles ahead). Each week the system runs a top-up so you always have that window in front of you. So if your list appears to "stop" a couple of months out, that's expected and correct — it isn't a missing end date or a fault, and you don't need to do anything. New cycles keep appearing as time rolls forward.

Detail

Think of it like a calendar that fills itself in rather than one you have to populate to infinity:

  • When you set up a recurring inspection or job (or a routine), Civic.ly generates the upcoming window of occurrences straight away — about 12 for a weekly cadence, 20 for daily, 12 for monthly. It deliberately does not create years of tasks in one go (that would clutter every list with thousands of far-future items).
  • A scheduled top-up runs automatically each week and adds the next cycle(s) onto the end of the window, so the horizon keeps moving with you. You'll always have roughly the same number of upcoming occurrences visible.
  • This is why a brand-new weekly routine might show occurrences out to, say, the end of next month and then nothing beyond — that's the edge of the current window, not the end of the schedule. Leave the recurrence end date blank and it simply continues indefinitely (see Should I set a recurrence end date on a routine, or leave it blank?).
  • The point of the window is that it's also far enough ahead to be useful: if you need to add a note or a special instruction to a specific occurrence a few weeks out, it already exists for you to open and edit.

If you want to focus on what's actually due rather than the whole window, filter the list — due today / due this week, with hide completed on. On the mobile app the operative's list works the same way, sorted by due date. See What's the recommended way for an operative to use the mobile app each day?.

Watch-outs

  • "It stopped at July" is normal. A weekly routine with no end date that only shows a couple of months of occurrences is at the edge of its rolling window — it will keep extending. Don't add an end date to "fix" it; that would actually stop it.
  • A long upcoming list is the routine, not duplicates. A weekly routine over, say, eight play areas will show a lot of upcoming occurrences (≈12 cycles × the assets in each). That's the window doing its job — group/triage with filters rather than worrying it's over-generated.
  • If a routine genuinely stops topping up (the window shrinks week on week, or future cycles for one routine vanish while others are fine), that is worth raising with us — it points to a generation issue, not the normal buffer behaviour.
  • The exact window sizes can change as the product evolves; treat "≈12 weekly / 20 daily / 12 monthly" as guidance, not a contract.