What's New

Bugfixes and minor changes

• Fixed a schedule member’s availability preferences depending on how their shifts or availability were structured. A blocked or preferred period now counts the same whether the shift it overlaps is a single entry or split into several parts, and likewise whether it was recorded as one availability entry or several.
• Fixed attribution for swapped or reassigned shifts. These now remain attributed to the shift type they were originally assigned from in all balance calculations.
• 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 denied 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 after a single rate limit denial will now be considered successful when subsequent retries complete without error. A connection is only considered degraded or stalled when no progress can be made for 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.

Older changes are listed by month below.