Why Have Email Triggers in Older Workflows Stopped Receiving Data?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Has something changed with E-mail triggers in older workflows? Yesterday around 1:29 pm CST both our e-mail triggered workflows stopped receiving data. If I try to send an e-mail to them, it is never received.

2

My E-mail triggers suddenly stopped since yesterday too. If I try to send an email to them - it’s never received too… Any information what is going on ? I can’t also edit workflows with E-mail triggers …Edit button is missing. Other workflows are editable but those with E-mail triggers aren’t. … I think that the problem is with V1 workflows at the moment

3

I copied my workflow to a new one and got a new e-mail address andit also doesn’t work. Let me see about changing to a V2 workflow

4

I also have active V2 workflow with Email trigger - it is working fine and is Editable. V1 workflows with email triggers are currently impossible to edit nor working

5

Something is going on. I tried to create a V2 workflow and the “Creating Workflow” circle has been spinning for 4 minutes now.

6

On V1 workflows with Email triggers - can you actually Edit the workflow now ? At my end the Edit button is missing…

image.png

7

I can edit the action step

8

I noticed the V2 e-mail is of the form @upload.pipedream.net. I just sent an e-mail to my V1 and added the upload. in front of pipedream.net and it was received.

9

Except it isn’t coming in as a normal e-mail. It’s missing the subject, the body. The data is there in the headers, and the content is referenced in an S3 file.

10

This is how an e-mail used to be received

image.png
image.png760×424 16.4 KB

11

Sending to the same address doesn’t work, but sending to the address with @upload.pipedream.net, it looks like this:

image.png

12

adding upload. triggers, but there is no html email inside and is not working for me

image.png

13

Same here. They broke something…

14

confirmed and looking into it

15

Thanks :+1:

16

This should be fixed, apologies for the issue and the delay

17

Thanks, it’s working now. Pipedream is usually 100% reliable, so we checked everything else on our end before thinking it could be the problem.

18

it was a subtle bug. We also had alarms on this issue but hadn’t integrated this specific one into our paging system, so missed the alert. Hopefully we can improve both of these issues on our end!