I’ve got an Indico 2.0.3 install that I’ve inherited which seems to be failing to send notifications.
The report I got is from our programme committee indicating that when they accepted a contribution, with the ‘send notifications to submitter’ checkbox checked, no notification was sent out. They also did not receive any notifications to the admin email addresses.
The submission notifications for Call for Abstracts, in Abstract Acceptance, is set to ‘Accepted as no type’. The person reporting the problem indicates that they were accepting the abstract with no type assigned, and that this has been their workflow in the past. It seems to me that based on the behaviour they want that ‘any type’ might be a better configuration option, but I agree that based on that configuration this should have sent out notifications.
I see no activity in the log that indicates any sort of notification being sent. Although, I don’t see a clear indication in the log of where the abstract in question was accepted either, so it’s possible Indico doesn’t log that type of activity… ?
The relevant snippets of
root: level: INFO handlers: [other]
handlers: indico: class: logging.FileHandler filename: indico.log filters: [indico] formatter: default celery: class: logging.FileHandler filename: celery.log filters: [celery] formatter: simple
I’m not entirely sure where to go from here with troubleshooting. I don’t see anything obviously wrong in the configuration, and there are no errors logged to the Indico logs, celery logs, or redis logs.
I haven’t yet found a way in the interface to re-trigger notifications, so even if I found a thing to change, I’m not sure how I’d test whether it fixed the problem.
And, unfortunately, I can’t seem to find a copy of the documentation for 2.0.3 … it looks like when readthedocs.io is updated, old versions of the documentation are overwritten.
Can anyone point me in the right direction to figure out what’s misbehaving here?