KamoCRM

Remove the recurrence control, which discarded what it collected

Fixkamo-internal
Shipped
26 ஆகஸ்ட், 2026 அன்று 6:17 AM UTC
Author
kamo
Commit
43afe74

The switch, frequency select and occurrence count rendered on the calendar page and reached no payload: composeDraft never read them and onSave never sent them. A member could set a weekly repeat, save, and get one event with no error and no warning. Nothing on the platform expands a recurrence rule, no endpoint accepts one, and CreateEventRequest has no field for one, so the control could not have worked. The entity columns and the RecurrenceRule type stay - they are inert and they are where an implementation would start. The lead callback composer hid the section explicitly, so its hide array loses the member too.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing