Richer Postmark Plugin error

Need help
1

@ZeroqodeSupport @ZeroqodeTeam

Hi guys, the plugin is causing an odd error.

I have a button that has two options to sending an email using the plugin

  1. If users ‘send emails with own domain’ is yes (meaning the Sender Signature is setup with Postmark)
  2. If users ‘send emails with own domain’ is no (the email is sent using my apps email address

A user had previously had this set to ‘yes’. I updated her setting to ‘no’ via the backend recently and the Sender Signature has been removed.

So the emails should now be sent using our generic email address.

However it is flagging this error, even though it’s triggering at the correct condition and searching for the users old domain.

I have tested this from other accounts (that have always been set to ‘no’) and have no issue. The issue seems to be that it was previously set to yes for this user.

I hope this make sense but if you need further information please let me know. Your support is greatly appreciated.

The condition that states if sent from our app email:

12e0356b4182346abc5f889746bbb8412a437b84
12e0356b4182346abc5f889746bbb8412a437b841636×492 40.3 KB

Error:

93122781bf05963c0d234fdf9857dc8b6616e2eb
93122781bf05963c0d234fdf9857dc8b6616e2eb912×856 104 KB

2

Hi @LA81638,

Thanks for reaching out! :pray:

We’ve recently updated this plugin with several modifications. Could you please confirm that you are using the latest version? If not, we recommend updating it and testing again.

Additionally, are you using a free or paid Postmark account? We’ve noticed this error tends to occur on free accounts when the email is not added to the Sender Signature.

Looking forward to your response!

Best regards :sunflower:

3

Hi @ZeroqodeSupport, thanks for coming back. Yes the plugin was completely up to date and I have a paid Postmark account.

4

Hi @LA81638,

Thank you for the details :pray: Could you please provide us with screenshots or, even better, a video recording using a tool like loom.com? Please show us how you’ve set up the plugin actions, including what information is passed to the action fields with the Bubble debugger active. This will help us better understand how the error occurs.

We will do our best to recreate this issue and resolve the behavior!

Best regards :hibiscus: