Yes! It has been happening ever since the High Sierra 10.13.4 update. See the attached thread I started where lots of other people are commenting on the issue. If you can, contact AppleCare and ask for a senior service advisor for them to document the issue and send it to engineering. We are trying to get enough people to complain that Apple addresses the issue in a future software update.