Hi @vini_brito, my users are getting this error, please can anyone help me understand the issue.
Iâm getting it everytime an email is sent with an attachment
TIA
Hi @vini_brito, my users are getting this error, please can anyone help me understand the issue.
Iâm getting it everytime an email is sent with an attachment
TIA
I have never seen this error before, but probably is a Bubble issue since other server side plugin actions from other plugins are showing the same problem.
Report that to Bubble, please, and insist it is not a plugin-specific problem when they try to redirect you to âthe plugin authorâ.
I am getting this too! All my emails have stopped working since a few hours ago. But its ALSO AFFECTING AMAZON SES emails! So itâs not plugin specific! Must be a bubble problem!
No transactional emails are being sent. Really annoying. grrr. Have written to bubble support.
Wonder whatâs happened.
Ok thanks for reply. Iâve messaged Bubble support
I have reached out to Bubble engineering and got an answer - they are working on a fix.
Thatâs great everyone! Iâm sure they will get this sorted out pretty soon.
Hi @vini_brito ,
will our emails be impacted in any way when we are using this plugin after the changes to be done by Postmark ( Static IP Deprecation: Postmark will no longer support IP allow-listing for our API ) ?
Link to the update:
@ahmed.khodeir.87, no it shouldnât
Thanks @johnny !
Iâm trying to understand the utility of this app over simply sending a post via the API Connector? doing so would also allow for different variable names (easier to then format in Postmark) and tags, etc. What am I missing?
@jacob10 Itâs just a quick drop-in replacement for the default Send email action. Nothing too advanced just works.
Also has some logic like when you donât give any âCcâ recipients it wonât send a null value like
âCcâ:"", in the POST body (yes this can be done with the API Connector too)
I have what appears to be a unique situation and hoping there is a good solution. I have an approval process where the next approver gets an email with a button in the email that they can click and when clicked, it will open up a web browser to my application that will trigger various events based on various requirements. The user doesnât need to do anything beyond just clicking the Approved Button.
This was working great until one customer implemented email security features where a robot will open every single email and on top of that will automatically test click links that are in the email.
So I am looking for a way to still have a button in the email that the user can click to approve in their email, but my application needs to know when it was the robot and NOT approve or do anything, but when it is the human, then approve and do all the required steps.
We can obviously force the user to actually do an action in the browser, but the goal here is to make the approval process as simple/easy as possible and not force the user to take additional steps after clicking the one button.
Thatâs a nice challenge! Hmm, I would start by profiling the browser, checking USER AGENT and things like that, lots of plugins offers you that info and many more.
See if you can differentiate the robot from real users.
Also, there is one variable that legit robots set to âyesâ to signal they are bots, it is called âweb driverâ, probably that bot will have that on, seek ways to check it.
@maw
@vini_brito I was wondering if there was a solution to this please? Thanks in advance 
@lisaalger Are you saying itâs behaving differently when itâs run directly vs schedule workflow? Cause that doesnât make any sense since itâs the same action
Hi ya @tylerboodman, as I have the BBCode > HTML element on a page when I send the email then it formats the text in the email. As I canât add that element to the backend workflow my emails arenât formatted correctly when sent through a backend workflowâŚhope that makes sense, just having my first coffee 
Well when you are scheduling the API workflow, you can include the BBCode there by passing it through as a parameter (add a new parameter to the API workflow (text))
Maybe thatâs what you want?
Ah can I, I didnât realise that
Will do that now, thanks so much