@jigsaw @brismith It sounds like you may have encountered the same issue as in a different thread. Here’s that thread and the fix:
If you have steps you took where you saw the issue, let us know.