A connection failure should not change a preference
On October 3, I corrected a confusing behavior in STEPN Forge: a temporary service failure could turn off alerts or erase the saved choice to receive them. A person who had enabled notifications could return to a different setting without having changed it. The interface was treating an unsuccessful check as though it were a deliberate decision by the person using the application.
The correction separates a saved preference from the application's ability to confirm its current operating state. A temporary failure to check owner access now leaves the preference intact and explains that verification will be retried. Confirmed sign-out or revoked access still disables the active state. The distinction matters: preserving someone's choice does not mean pretending that access or delivery has been established when the service cannot be reached.
Automatic notification synchronization follows the same principle. If saving the subscription fails, the application keeps the opt-in and reports that synchronization is incomplete. It can try again with the next price update. Owner verification also has a bounded retry and can recover when the connection returns. Those paths preserve the original decision while making the interruption visible, instead of silently asking the user to rediscover and restore a lost setting.
The change was merged that day after regression checks exercised the actual application handlers with controlled responses. The checks covered temporary failure, recovery, confirmed loss of access, sign-out during an outstanding request and an explicit request to disable alerts. They also checked that recovery would not reverse that explicit disable action. This evidence supports the behavior of those paths; it does not establish that a notification reached a real device or that an unrelated infrastructure warning was resolved.
Reflection
A preference records intent, while a connection check records what the application currently knows. Keeping those separate made STEPN Forge's interruption behavior easier to explain. The useful result was preserving a deliberate choice without hiding uncertainty about whether the service was ready to act on it.