Verified email address not receiving body of email sent from worker

For Workes & Pages, what is the name of the domain?

bcsquared.tech

What is the issue or error you’re encountering

I have 3 verified destination email addresses, 2 of which are mine (main and alias) and 1 which is not. I have a scheduled worker that does some work and then sends an email with the results. If I send the email to my main, with my alias cc’d, and vice versa, I receive the results just fine. If I sent the results to the 3rd email (not mine) with my alias cc’d, the recipient receives a blank body and my cc’d alias does not even receive an email. There are no errors given by Cloudflare as real-time logging says the job completed successfully. What could be going on?

What steps have you taken to resolve the issue?

  • made sure all 3 emails have been verified through email routing settings
  • sent multiple messages successfully with my main email as the sender and my alias as the cc, and vice versa
  • made sure my 3rd email was spelled correctly
  • added SPF and DMARC to my domain as my personal domain is through google.com
  • sent the email with the 3rd email as the Cc and my main as the recipient

What are the steps to reproduce the issue?

Set the 3rd email address as the recipient or CC, set up a cron job to run the worker a few minutes past the current time in UTC, and await the results.

Same issue observed. In my case I have a cron worker send an email to my verified email address but the email has no body. I followed the code example here.

1 Like

Glad I’m not the only one. I followed that code example as well. Do any other of your verified addresses receive the body, just not certain ones?

Turns out the body is blank for an outlook address, but shows up fine for gmail. This makes me believe that cloudflare email has some weird compatibility issue with some email providers.

I’m glad (well, not glad) that you’re seeing the same issue. I will look into sending an email through my Gmail and forwarding that to my 3rd party instead. Hopefully, that works.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.