This would work great, and my understanding is that you are correct. If you control when and how the core reconnects to WiFi (or the cloud) then you can control how long user code is blocked, so Semi-Auto wouldn’t do “auto-reconnect” and thus you can control when it reconnects.
This actually might work. What I could do also is if WiFi drops, and my timer (of 1 minute) is triggered, if the Core then can’t send the data off (via WiFi) it can save it on the SD and the file can just grow larger and larger, until it does connect with WiFi then it can send all the data that was on the .txt file. Then just wipe the contents of the file (?*) and rinse and repeat. Also that way in-between the timer trigger I can attempt a WiFi connect for lets say, 10-15 sec, then if it doesn’t connect break the loop and go back to user code, am I on the right track here?
Also just saw that you posted while I was typing my lengthy ass reply, I am storing counting data on an interrupt, every time interrupt is triggered count, which is why I don’t want it to get blocked off at all; however, if blocking for a couple seconds means eliminating a second spark Core, I can adjust until the Photon comes out.
?* - to eliminate the contents of a txt file on a SD, do I just open the txt file and write to it, then I write nothing and then close the file? I saw this on another forum on how to delete contents, without deleting the file, and was wondering if it’s correct.
Thanks again for all the help