Workflow Emails not sent

[karimj]

I have a Workflow (e.g. send an Email 1 day after the event), but the email is never sent.
When I look in the DB in the table WorflowReminder I see an entry, with scheduled = FALSE.

(I am using the cal.com via docker, currently v.3.9.1-sh)

Is there a setting missing? Is that a bug? Any help would be greatly appreciated.

[karimj]

Update:
I upgraded to the newest version now (4.4.5)
Now the emails show up in the DB with scheduled = TRUE and also have a referenceID, but nothing is sent out.
(all other emails work as expected)

[dosubot[bot]]

Hey @karimj! I'm here to assist you with any bugs, questions, or contributions. Let's work together to resolve this issue!

There are a few things you can check to troubleshoot the issue with workflow emails not being sent in cal.com:

1. Configuration Settings: Ensure that your email server and SendGrid configurations are correctly set up in the .env file. This includes the SENDGRID_API_KEY, SENDGRID_EMAIL, and other SMTP settings if you're using a different email service ^[1].

2. Conditions for Sending Emails: In version 4.4.5, workflow emails are sent based on specific conditions, such as authentication, configuration, and trigger events. Make sure that these conditions are met, including having a valid API key and configured SendGrid API credentials ^[2][3].

3. Error Handling and Logs: Check if there are any errors logged during the email sending process. Although specific logging mechanisms weren't detailed, you might want to look into your server logs or any error logs generated by the application to identify potential issues.

4. Similar Issues: There are similar issues reported, such as [CAL-4512] Workflow email sometimes not sending, which is still open and might provide additional insights or solutions.

If these steps don't resolve the issue, you might want to investigate further into the email scheduling mechanism and ensure that all dependencies and services are running correctly ^[2][4].

To continue talking to Dosu, mention @dosu.

Written by @dosu, approved by dosu-customer-success