We have a recurring problem where the New Issue Released email is sent out at random intervals after an issue is released. Looking though the access logs, there is no regular pattern of activity that appears to trigger the email, except that someone is doing something to a submission. A few times it has been a new submission, twice it has been someone editing a submission, and once when an editor unscheduled, edited metadata (I think) and then rescheduled a published article. Inspecting the the email logs shows that the spurious emails only go to the managing editors and the person who was submitting/editing.
What is the actual trigger, in the code, to send the New Issue Released email?
Are you (or someone with your journal) unpublishing and publishing issues? Sometimes if someone is unpublishing, making edits to articles, and then republishing the issues, they may inadvertently select the checkbox that issues the notification to all users about the new issue, when republishing the issue.
I thought so, too, at first, but fortunately the unexpected emails are only going to the editors and to the person who was either adding or editing a submission. When an issue is truly released, then the new issue notification goes out, as expected, to all the users who signed up for notification.
The latest one, this morning, appears to have been triggered by a new submission. I had thought that somewhere the trigger for the new issue email might also be buried in a submission (sub-)process, but it doesn’t happen every time, so it going to be difficult to track down.
Thanks. I have one more piece of information: we got another instnace this morning, and looking back, the last five submissions have triggered these new issue emails. That narrows the search a bit.