I have a longer sequence on a front end flow. in the middle, I have to send a confirmation email to the client (top box) and after that, immediately to the space. The first one gets sent, but the second one to the space never gets sent. (It’s setup to my personal email to test).
I have to mention the two emails are setup the same way, with Sender Name: admin-no-reply@bubble.io . First step email arrives, second deosn’t.
However, when I debug it, my personal email shows up in the debugger when the step 11 (email space)is running .
hmm, then trying switching the order of the two steps. If the first one is sent and the second isn’t, it’s probably an issue caused by some buffer period between emails sent from bubble, maybe anti-spam or security measure.
if, on the other hand the same email isn’t being sent, you need to investigate the workflow closely and try to figure where the issue is.
Change the order of the emails to see if the one that used to be first, now becoming the second, ends up failing.
Run a test by sending to a different email in the second step to understand whether it sends the first email and also sends the second in this case.
And lastly, I would move these email-sending calls to the backend, then trigger the first one there to send at the “current date time”, and for the second one I would add 30 seconds or 1 minute to see if it arrives.
Try running these tests to see if anything changes.
Thanks mate. So tried 1 & 2 and didn’t work. Should I try 3 then by calling an API in the backend and send the emails from there? This is so weird. Why would one email work but not the next one in the front end flow?
When running this through API workflows, each call becomes its own scheduled task in Bubble’s server queue. This ensures that all executions are logged and run correctly. That’s probably why it worked in the API workflow and not on the front-end. Because when we try to run the two email-sending actions in a front-end workflow, they are executed at the same time if there’s no dependency between them. This may have caused Bubble to see them as “identical” actions and simply ignore the second one. We could verify this better if we tried creating a custom event on the front-end for sending the email, and then you “scheduled” this custom event, maybe that way the email would also be delivered.
But anyway, having this action in backend workflows is a best practice. You configure it however you want there, and use it throughout the entire app.
hey @carlovsk.edits . so I set both of emails in the backend, triggered by an API workflow as suggested. I still get just one email, for the client. any idea hat’s going on? this is so annoying.
below the backend flow containing the two emails. called from the frontend flow, doesn’t work.
I also tried putting the email to the client in the frontend flow and then setup the api workflow to a backend flow to send other email, to the space, and nothing. (below) Moreover, the API workflow is set to wait 30 seconds before activating the back end flow and the bastard still doesn’t want to send that email! I. tried 3 differrent email address for the space and nothing.
I just ran some tests here in my app to try to understand things better. Funny enough, I added a button, and inside it I placed two email-sending actions to the same recipient (my email), and it worked.
So, your first alternative, and the one I sent you, all of those were supposed to work. There’s nothing wrong with the body of your email?
At this point, I think it would be interesting for you to get in touch with Bubble support.
