Set limited or unlimited recurrence cycles
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Control when appointment recurrence stops automatically or continues until staff end it.
What you’ll accomplish
Control when appointment recurrence stops automatically or continues until staff end it. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
Limited recurrence stores a maximum cycle count and tracks generated cycles.
Unlimited recurrence continues through cron until the recurring flag is stopped or another condition prevents generation.
Skipped unavailable occurrences and generated-cycle handling should be reviewed in module history.
Follow these steps
- Select the recurrence frequency.
- Select limited or unlimited mode.
- For limited mode, enter the permitted cycles.
- Save.
- Monitor generated records and stop unlimited recurrence when no longer required.
Settings to check
Check it worked
After this workflow completes, Pixie CRM keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Pixie CRM database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Common mistakes to avoid
- Do not use unlimited recurrence without ownership and review.
- Stopping future generation does not remove existing children.
- Check provider changes over long-running recurrence.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
