Yes I have verified this message does not appear to break functionality. I am moving forward ignoring it at this time and it seems to be causing no issues.