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

[mf1511]

hey @dosu,

i still cant make the reminders work.
In my variables:
ENABLE_TASK_SYSTEM=true
CRON_ENABLE_APP_SYNC=true

My cron job:
// Email reminders - every 1 minute
new CronJob(
"0 */1 * * * *",
async () => {
await callCronEndpoint(
"/cron/workflows/scheduleEmailReminders",
"Email Reminders"
);
},
null,
true,
"UTC"
);

I can see my reminders:
railway=# SELECT
id,
"bookingUid",
"scheduledDate",
scheduled,
cancelled,
method
FROM "WorkflowReminder"
ORDER BY "scheduledDate" DESC
LIMIT 20;
id | bookingUid | scheduledDate | scheduled | cancelled | method
-----+------------------------+---------------------+-----------+-----------+--------
484 | oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 12:48:00 | t | | EMAIL
483 | oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 10:58:00 | t | | EMAIL
485 | oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 10:45:00 | t | | EMAIL
479 | oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 10:36:00 | t | | EMAIL
482 | oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 10:16:00 | t | | EMAIL
480 | oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 09:46:00 | t | | EMAIL
481 | oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 08:46:00 | t | | EMAIL
(7 rows)

railway=# SELECT uid, "startTime", "endTime", title
FROM "Booking"
WHERE uid = 'oAqDWFJgzYZ5BaxTBwsfXY';
uid | startTime | endTime | title
------------------------+---------------------+---------------------+---------------------------------------------------------
oAqDWFJgzYZ5BaxTBwsfXY | 2025-10-05 10:46:00 | 2025-10-05 10:48:00 | 2min entre M - DFY et Ma - DFY
(1 row)

railway=#

but i never receive the emails.

There's a timezone problem maybe? Im utc+2

and in your repo code, we can only trigger the events that are there for the next 2 hours

export async function getAllUnscheduledReminders(): Promise<PartialWorkflowReminder[]> {
const whereFilter: Prisma.WorkflowReminderWhereInput = {
method: WorkflowMethods.EMAIL,
scheduled: false,
scheduledDate: {
gte: new Date(),
lte: dayjs().add(2, "hour").toISOString(),
},
retryCount: {
lt: 3, // Don't continue retrying if it's already failed 3 times
},
OR: [{ cancelled: false }, { cancelled: null }],
};

const unscheduledReminders = (await getWorkflowReminders(whereFilter, select)) as PartialWorkflowReminder[];

return unscheduledReminders;
}

Im sending my emails with SMTP and everything works on that side. i can receive the other emails.

How to properly use the reminders workflows please?
Im on Railway

thanks

[dosubot[bot]]

Here are the key things to check for workflow reminder emails on Railway:

1. Cron job setup on Railway: Railway doesn’t run Cal.com cron jobs automatically—you need an external scheduler or a separate Railway service (using apps/web/cron-tester.ts) to trigger /cron/workflows/scheduleEmailReminders with the correct API key and secret. Make sure your cron job is actually running and authenticated with CRON_API_KEY and CRON_SECRET set in both services. Details on this setup are discussed here.

2. Logs: Check logs for the scheduleEmailReminders endpoint and the emailReminderManager service for any errors, warnings, or debug output. Failures in the workflow reminder pipeline (like provider errors, misconfigurations, or missing verification) should show up in logs. If verifiedAt is missing for a workflow step, the reminder won’t be sent and you’ll see a warning in the logs (source).

3. Timezone: Make sure scheduledDate in your WorkflowReminder table is stored in UTC and calculated in UTC, not local time. The code compares scheduledDate to new Date() (UTC), so mismatches can cause reminders to be missed.

4. Environment variables: You need ENABLE_TASK_SYSTEM=true, CRON_ENABLE_APP_SYNC=true, CRON_API_KEY, and CRON_SECRET set. Also, check that emailsEnabled is true for your workflows if applicable.

5. Manual test: Try manually triggering the /cron/workflows/scheduleEmailReminders endpoint and watch the logs and database for errors or email sends.

If you check these and still have issues, share any relevant log output or error messages for deeper troubleshooting.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[mf1511]

@dosu

j'ai mon service /cron/workflows/scheduleEmailReminders:
new CronJob(
"0 */1 * * * *",
async () => {
await callCronEndpoint(
"/cron/workflows/scheduleEmailReminders",
"Email Reminders"
);
},
null,
true,
"UTC"
);

j'ai ENABLE_TASK_SYSTEM=true, CRON_ENABLE_APP_SYNC=true, CRON_API_KEY, and CRON_SECRET qui sont set up.

ça a l'air de fonctionner mais j'ai maintenant cette erreur:

@calcom/web:start: {"0":"Email sending failed","1":{"nativeError":{"name":"PrismaClientKnownRequestError","code":"P2002","clientVersion":"6.8.2","meta":{"modelName":"Task","target":["referenceUid","type"]}},"name":"PrismaClientKnownRequestError","message":"\nInvalid prisma.task.create() invocation:\n\n\nUnique constraint failed on the fields: (referenceUid,type)","stack":[{"fullFilePath":"/calcom/apps/web/.next/server/chunks/29706.js:114:8027","fileName":"29706.js","fileNameWithLine":"29706.js:114","fileColumn":"8027","fileLine":"114","filePath":"/.next/server/chunks/29706.js","filePathWithLine":"/.next/server/chunks/29706.js:114","method":"hH.handleRequestError"},{"fullFilePath":"/calcom/apps/web/.next/server/chunks/29706.js:114:7087","fileName":"29706.js","fileNameWithLine":"29706.js:114","fileColumn":"7087","fileLine":"114","filePath":"/.next/server/chunks/29706.js","filePathWithLine":"/.next/server/chunks/29706.js:114","method":"hH.handleAndLogRequestError"},{"fullFilePath":"/calcom/apps/web/.next/server/chunks/29706.js:114:6794","fileName":"29706.js","fileNameWithLine":"29706.js:114","fileColumn":"6794","fileLine":"114","filePath":"/.next/server/chunks/29706.js","filePathWithLine":"/.next/server/chunks/29706.js:114","method":"hH.request"},{"fullFilePath":"/calcom/apps/web/.next/server/chunks/29706.js:126:6321","fileName":"29706.js","fileNameWithLine":"29706.js:126","fileColumn":"6321","fileLine":"126","filePath":"/.next/server/chunks/29706.js","filePathWithLine":"/.next/server/chunks/29706.js:126","method":"async f"},{"fullFilePath":"/calcom/apps/web/.next/server/chunks/24135.js:3:5271","fileName":"24135.js","fileNameWithLine":"24135.js:3","fileColumn":"5271","fileLine":"3","filePath":"/.next/server/chunks/24135.js","filePathWithLine":"/.next/server/chunks/24135.js:3","method":"async j.create"},{"fullFilePath":"/calcom/apps/web/.next/server/chunks/24135.js:9:2552","fileName":"24135.js","fileNameWithLine":"24135.js:9","fileColumn":"2552","fileLine":"9","filePath":"/.next/server/chunks/24135.js","filePathWithLine":"/.next/server/chunks/24135.js:9","method":"async f"},{"fullFilePath":"[undefined]","fileName":"[undefined]","fileNameWithLine":"[undefined]","fileColumn":"[undefined]","fileLine":"[undefined]","filePath":"[undefined]","filePathWithLine":"[undefined]","method":"[undefined]"}]},"_meta":{"runtime":"Nodejs","runtimeVersion":"v18.20.8","hostname":"293e393580a4","name":"[undefined]","parentNames":"[undefined]","date":"2025-10-05T14:12:10.926Z","logLevelId":5,"logLevelName":"ERROR","path":{"fullFilePath":"/calcom/apps/web/.next/server/app/api/cron/workflows/scheduleEmailReminders/route.js:56:29923","fileName":"route.js","fileNameWithLine":"route.js:56","fileColumn":"29923","fileLine":"56","filePath":"/.next/server/app/api/cron/workflows/scheduleEmailReminders/route.js","filePathWithLine":"/.next/server/app/api/cron/workflows/scheduleEmailReminders/route.js:56","method":"[undefined]"}}}

[mf1511]

@dosu
A t'on besoin de Redis ?

[mf1511]

@dosu

Voici ce que me donne GPT:
"
Ce que je te suggère maintenant :

Cherche dans le repo Cal.com sur GitHub pour "task worker" ou "task execution"
Regarde les variables d'environnement liées aux tâches dans leur documentation
Cherche comment d'autres ont déployé Cal.com selfhosted avec des workflows fonctionnels

Je me suis peut-être focalisé sur Redis parce que c'est une solution standard pour les queues de tâches, mais Cal.com utilise peut-être un autre mécanisme.
Le problème reste : les tâches ne s'exécutent pas. Il manque une pièce de configuration que je n'ai pas identifiée avec certitude. Désolé de t'avoir fait perdre du temps si Redis n'est pas la bonne piste."

Apparement mes taches sont créées mais jamais envoyées