It sounded like file access early on in the thread. Then you confirmed it in the log.
Can Jamie tweak the CW code to rename the last read file as data-bak.txt (or what ever format it is) then write a new one. Each time renaming the previous one, before writing the new one? Then have SGP access the .bak file? Also if it’s checking at 120 seconds. Changing that to 240 would make the chance of file access being less frequent. Also what about changing the CW update/file write time?
I have a CW too and if it rains, I really don’t want a 4-5 minute delay. Things could be soaked in 60 seconds. Might be something to throw at Jamie via email or in the CW forum? I’m just setting mine up for safety and I’d first like to get it to close for clouds/unsafe… I just found it only does this DURING a sequence? I’m more often open not during a sequence than during. 50/50 at best.
Another option would be the READ of the file (that is being written) to do a error check for a open file and (on error) wait 10 seconds and try again. That would always get by the problem.