@glenn Just upgraded to 3.15.2 yesterday, so really hard to say.

@glenn That sounds like a reasonable course of action. Microsoft has been known to screw stuff up on occasion, and I think WMI isn't flagged as a high...

@glenn - I'll give that a try. I always forget about the IF feature. That should help.

@glenn - Ok, that makes sense. So how do I hide the whole thing if IPv6 isn't returning data? Like if the ProtocolAddress is blank due to not being ab...

@glenn I actually put it in both. I added it to the CMD item, with a timeout just longer than if I added all the individual timeouts in the script tog...

Still no issues. Looks like adding timeouts to the Invoke-RestMethod helped to resolve the issue. Interested to see how your threading code changes wi...

So far so good. Last time it glitched it wasn't immediate, so I'll continue to monitor.

I've just added a timeout value to the Invoke-RestMethod command in the PS1 section, limiting each attempt to 10s. That should keep the script under t...

See code block below. SET-SECTION=key:wan-ip-lookup,value:wan-ip-lookup.ps1 CMD=interval:300,color:55cc77,text:WAN Address,onload,no-wait:2,threa...

Yes, that was the only entry. I was able to right-click Quit, but that took quite some time actually complete. I rolled back to v3.13.2 for the time b...

@glenn Yes, I had the SET-SECTION, I just forgot to post it in my snippet of code. I'm glad you found the bug and I wasn't going crazy. 🙂