- Ya
- 2 Septemba 2026, 02:52 UTC
- Mwandishi
- Kamo
- Ahadi ya
- ea634f1
Emptying a custom label box and saving did nothing. The save built its payload from the labels that had text in them, so a box the org had just cleared was not mentioned in the request at all — and a request that says nothing about a status cannot remove it. The server echoed the surviving row back and the old label reappeared in the box, which is what made it look like the save had failed. buildStatusLabelPayload now says the removal out loud: a status that was saved and is now empty goes out with a blank label, which is the instruction to drop the row and fall back to the system wording. A status that was never customised still stays out of the body, and a label typed to match the system wording is read as no customisation rather than stored as a copy of the default. Saving also invalidates the shared label cache. It is filled once per session, so without this a label removed here kept showing on the pipeline, the lead view and the softphone until a full reload — the same bug wearing a different face.