Fixed

OnSched 3.24.6 — Reuse a deleted customer's email

Customers

Deleting a customer no longer keeps that email reserved. POST /v3/customer still restores the deleted customer when that email is submitted and no live customer has it. PUT /v3/customer/{id} can assign the email to a different customer in the same company.

If a live customer already has the email, POST /v3/customer and PUT /v3/customer/{id} return 409 with message Customer already exists for this company. Bulk create still returns 201. The conflicting item is reported with status 409 and that same message, and later items in the batch are still created.

V1 customer get, update, delete, appointment filters, and booking use that same 409 when restoring a deleted customer would duplicate a live email, or when the legacy id is already linked to a different live customer. V1 customer sync records the conflict and continues with the next customer. The deleted customer and the live legacy link stay as they were.

Resources

On Resource Info, Disable notifications now stays checked after save and after reload. Checking it stores that resource's notificationType as NONE (no appointment email or SMS to that resource). Unchecking it stores the selected Notification Channel, or Email when that channel is None.