On this page
What users will report, and how to recognize itQuestions to ask when triaging a tag-sync reportFor Support
What users will report, and how to recognize it
"The Update button on a user's calendar settings won't let me save."
Before this fix: if the user only added, edited, or removed a break time (and didn't touch any other field like opening hours, rooms, or closed days), Update stayed disabled — permanently, until they also touched some other field on the page.
After this fix: editing breaks alone now enables Update like any other change. If a ticket describes this exact symptom on a build that predates this PR, it's this bug — no workaround needed beyond "also click into another field," and no data was ever lost; the save was simply blocked client-side.
How to confirm the fix is deployed: open Settings → Users → (any user) → User Calendar Settings, add a break to any day, and confirm Update is clickable without touching anything else.
"A patient's tags don't match on WhatsApp" / "My WhatsApp automation isn't triggering for a tagged patient"
Before this fix: a patient's Patient Tags (visible on their profile and in Edit Patient) and the tags stored on their linked WhatsApp conversation could drift apart, because:
- Editing tags via a lead never pushed the change to the conversation.
- Creating a new patient from a WhatsApp chat never seeded the
conversation's tags from the ones chosen on the new-patient form.
After this fix: both paths now update the conversation's copy.
Important limitation to relay to users: this fix is forward-looking only. It does not retroactively repair conversations whose tags were already out of sync before the fix shipped. If a customer reports stale tags on an existing conversation, the fix alone won't correct it — the conversation's tags will catch up automatically the next time:
- the linked lead is edited (any edit that changes patientTags), or
- a new patient is created from that conversation.
If neither of those will naturally happen soon and the customer needs it corrected now, that's a manual data fix (escalate rather than promising a self-heal), not something the UI currently offers a button for.
Questions to ask when triaging a tag-sync report
- Is the tag mismatch on a lead's conversation or a patient's
own conversation? (They can differ — see WhatsApp Conversation Tag Sync.)
- Was the patient's tag change made by editing a lead, or by editing the
patient directly outside a lead? (Only the lead-edit and new-patient-from-conversation paths are covered by this fix.)
- What build/deploy date is the clinic on? If before this PR, it's the
known bug; if after and still mismatched, it's likely stale data from before the fix (see limitation above), not a new bug — but worth a fresh look either way.