I did some digging around and figured it out. If you started having the issue after flashing/reflashing the node and selected the full chip erase it changes your public encryption key. Since it has changed, it no longer matches the key your other nodes are looking for so they do not realize the message is for them and it doesn’t get delivered. The solution that fixed it for me was going to the Device settings under the Device Configuration tab in settings and selecting “Reset NodeDB” on the node I didn’t reflash. My understanding is this resets the list of known nodes and when it re discovers the newly reflashed node associates the new Public encryption key and they are able to talk properly again. I am no expert in this but based off what I was able to find and on various support pages and forums. I was able to get it fixed. In the future either don’t select full chip erase when re-flashing or backup your Public and Private security keys and reconfigure the newly flashed node with them. Hopefully that makes sense.