We investigate this issue and it seems that the problem is due to a bug in the software of the controller: After a power-cycle of the unit, it does not connect the server for new watering schedules. It happens randomly and more easy to occur when the network speed is low. A workaround is to force a connection by launching a manually run from the app after the power cycle. Basically after the controller is rebooted an online, start a manually run from the app and the controller should work as expected.
You device is running v1.1.1 firmware (check that in the app, settings->controller). This "reboot" issue has been fixed in a recent firmware update(v1.2.0). The update has not been pushed to all the devices but it will eventually. We are testing the new firmware and after it is verified and pushed out in a few weeks, the issue you reported will be resolved.