Remote gateway error status after renaming remote server

After renaming a remote server (okay, I fat-fingered it and had to rename it twice), I see a Defined_NeverConected status on the old names. Is there any way I can get rid of them, as they technically don’t exist anymore?

A restart of the gateway took care of it. It wasn’t a code red thing by any means, as everything was otherwise working. It just caught my attention.

On the bright side, now the guys I work with won’t see it and ask me what the heck is up. :wink: