when we click save it calls the https://api.cal.com/v2/atoms/schedules/schedule_id endpoint with our schedule_id and returns a success response, and soon after that it calls https://api.cal.com/v2/atoms/schedules and we get the correct data

but after we refresh the page, it again calls https://api.cal.com/v2/atoms/schedules, but this time the previous change is not there

The most likely reason your changes aren't persisting is that the payload sent to the backend is missing required fields—especially the name or schedule data. If these are omitted or malformed, the backend will return a success response but skip updating the availability, so the UI shows a false positive and the changes disappear after refresh. Double-check that your save logic always includes all required fields in the payload (details). This is a known pitfall in the current implementation: the backend does not reject incomplete updates, it just silently ignores them.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}