0

I am attempting to set up a Scheduled Reminder for Scheduled Activities (CiviCRM 5.20.2/Drupal 7).
I have a Scheduled Reminder set up as follows: Image of Schedule Reminders screen showing Phone Call reminder

This is setup to send to the Activity Assignees, 0 hours before a Scheduled Phone Call activity. It is enabled, and has a simple email message.

Under Scheduled Jobs, I can see that "Send Scheduled Reminders" (Job.send_reminder) is enabled, is running always, and the logs say it is successful.

Finished execution of Send Scheduled Reminders with result: Success (1)

If I then create an Activity of type Phone Call, set its status to Scheduled, set the time to 30min in the future, and assign it to myself, I will immediately get a system generated Activity Summary email. In 30min time I will not get a reminder from the Scheduled Reminder, with the template I defined.

Can anyone tell me why, or tell me where to look for more information? Are there logs which will show me if the reminder is actually being triggered, or if an attempt is made to send the email?

Improve this question
4
  • You could try changing it to 0 hours AFTER the activity time and see if that makes a difference?
    – RebeccaTregenna
    Apr 3, 2020 at 8:14
  • Thanks for the suggestion - unfortunately it still didn't trigger. I also tried setting repetitions, but they also didn't trigger.
    – danielrobertson
    Apr 6, 2020 at 3:40
  • OK, I have discovered the civicrm_action_log which I can view using phpmyadmin. All the reminders are visible there - all have an error "Failed to send message". This looks email related.
    – danielrobertson
    Apr 6, 2020 at 23:56
  • Continuing to debug - after switching to sendmail from direct SMTP to Amazon SES, we have discovered that the emails are being sent, but apart from the "To:" field, they are completely blank. No subject, no body. Has anyone encountered this?
    – danielrobertson
    Apr 8, 2020 at 23:10

1 Answer 1

Reset to default
3

OK, answering my own question after much investigation. This was a bitnami civiCRM stack and the crontab to run Job.execute was running as the bitnami user (our error), but needed to run as daemon. That is documented on bitnami's site: https://docs.bitnami.com/bch/apps/civicrm/configuration/configure-scheduler/

Strange behaviour as a result of this - cron seemed to be running fine, but it clearly didn't have permissions to send emails.

Improve this answer
2

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.