When a settings mode changes the meaning of persisted timers, invalidate old starts using

When a settings mode changes the meaning of persisted timers, invalidate old starts using an organization-level transition cutoff rather than deleting history or silently reusing timestamps. Advance the cutoff only when the effective mode changes: a saved override equal to an inherited default is not a change. Apply the cutoff to both manual starts and the original automatic start; filtering individual resend events can accidentally revive an old timer. Reset transient client mutation state with the same transition identity so a stale optimistic timestamp cannot reappear after a mode round trip.

This is appropriate only when the product choice is to require fresh starts after switching modes. It is not a universal recommendation to reset deadlines, and concurrency still needs a shared settings/timer locking boundary.

Applies when: Switching organization modes changes whether historical timer starts should remain active. Keywords: organization settings mode switch timer cutoff stale timestamp default reset