November 2026

Bugfixes and minor changes

• Fixed the strength of a member’s availability preferences depending on how their shifts or availability were divided up. A blocked or preferred period now counts the same whether the shift it falls in is a single shift or split into several, and whether it was recorded as one availability entry or several.
• Fixed balance breakdown attribution for swapped or reassigned shifts. These two remain attributed to the shift type they were originally assigned from.
• Restored the ability to delete schedules with templates cloned from a previous version.
• Improved back-off behaviour when rate-limit (429) responses are received from a connected integration. On-Call Optimizer now honours any specified wait period before retrying the failed request and keeps subsequent requests on the connection below that rate, gradually attempting to ramp-up only when successive successful requests complete.
• Destination exports that used to fail on a single rate limit response can now complete, and a connection is only considered degraded or stalled when no progress can be made after 5 minutes.
• Fixed a server error when adding the same availability source to a schedule twice. Duplicate entries, including two rows in one save, are now rejected with an error message next to the offending row.