-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Did you manage to get the console to trigger the email handler on the worker? #40
Comments
I'm not really in context of that anymore, but I just checked. Here's what I can say:
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/ |
Reading in the docs, I now remember that you have to access email workers through 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. |
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. |
Hi all, I have the same error how did you managed to test it? |
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). |
Thank you, how did you log the message? |
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?
The text was updated successfully, but these errors were encountered: