Question: Did you manage to get the console to trigger the email handler on the worker?

[bn-l]

I saw your question here on a stackoverflow scraper (SO doesn't rank at all on google for the error message: "Email Trigger not available to this workers").

Did you manage to get the console next to the code editor working?

[webbertakken]

I'm not really in context of that anymore, but I just checked. Here's what I can say:

• The repo is still a good working example
• I can open the "Edit code" view
• It shows a different error instead of malfunctioning altogether

.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-facade-1.js:14 Error: No fetch handler!
at facade_modules_fetch (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-loader.js:23:38)
at facade_invokeChain (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-common.js:16:10)
at Object.next (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-common.js:13:14)
at jsonError (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-facade-1.js:12:32)
at facade_invokeChain (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-common.js:16:10)
at Object.next (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-common.js:13:14)
at scheduled (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-facade-0.js:9:24)
at facade_invokeChain (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-common.js:16:10)
at facade_invoke (.internal-f0f1e173-d2b2-4572-b0f4-76f5471a5a8a-common.js:19:10)

• The interface for sending a test email seems to be gone entirely

i.e. instead of this:

There's now this:

Looks like they've moved from their proprietary editor to a webbased implementation of VS Code, which no longer has any notion of emails.

Recommend using the official docs @ https://developers.cloudflare.com/email-routing/email-workers/

[webbertakken]

Reading in the docs, I now remember that you have to access email workers through Email > Email Routing > Email Workers to access it through the email specific editor, which seems to still be the old editor.

I see that the email trigger is not available still. However that might be because I haven't updated my wrangler config for a while.

[webbertakken]

Just updated all deps #41 and wrangler and wrangler config #42.

The result is the same in the console: Email Trigger not available to this workers

So I guess the answer is that CF don't have that UI working yet.

I can confirm that my discord debug channel is still receiving

[bn-l]

Wow huge thanks for A: getting back to me and B: such a thorough response. Very appreciative.

So as it stands now the console is definitely bugged but emails are triggering the "email" handler (this is from my own testing also).

I hope someone googling that error finds this thread.

[badilaa-ppb]

Hi all,

I have the same error how did you managed to test it?

[webbertakken]

For unit / integration testing, there's the automated tests that you can find in the repo.

For the end-to-end test I just sent an email myself and verified that it sent the message to the discord channel (see screenshot above).

[badilaa-ppb]

Thank you, how did you log the message?

[cschanhniem]

For anyone still hitting this: Cloudflare's email trigger test UI in the Workers dashboard is still not functional for email handlers (the trigger type simply isn't available in the quick edit / test tab). The reliable local alternative is wrangler dev with a custom test harness that constructs a ForwardableEmailMessage-shaped object and calls your handler directly.

A minimal vitest/jest setup looks like:

import { unstable_dev } from 'wrangler';

const worker = await unstable_dev('src/index.ts', { experimental: { disableExperimentalWarning: true } });
// wrangler's unstable_dev doesn't support email events directly,
// so call your handler function with a mock message object instead

The simplest approach is to export your handler logic separately from the email export, so it can be unit-tested without the Cloudflare runtime. The existing tests in this repo already do this — run yarn test and they pass without any Cloudflare account.