@Brian-McG I believe the rare scenario where this could occur is fixed in the upcoming 5.1 update.
When you have that version (expected release week of May 18th) and it does occur, please create a support ticket with more information / possible ways to reproduce the issue.