@Brian Lemanczyk Apologies for the delay in response and all the inconvenience caused because of the issue.
I had discussion internally and below is the response I got from our internal team:
This is a known bug in diagnostics as informed by our internal team. It only impacts the diagnostics test case, the customer can simply ignore this error. Internal Team is working to fix it, we currently don't have any specific ETA for same but rest assured it is being worked upon.
Hope it helps!!!
Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.