# Some Emails through Postmark are not working after working fine for months

**URL:** <https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531>\
**Category:** Need help\
**Created:** [December 17, 2022, 11:07pm UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531 "2022-12-17T23:07:40Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![eric10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/eric10/32/111185_2.png) [@eric10](https://forum.bubble.io/u/eric10)\
**Post date:** [December 17, 2022, 11:07pm UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/1 "2022-12-17T23:07:40Z")

</div>

One of the things I despise about this whole process of creating an app with Bubble is the emails. I’m using Postmark, and it took a lot to get it working, but for months now it was working without issues.

I’ve noticed some email systems that were working fine are now not working. Did something change which would require me to change something? Why all of a sudden are things not working now? I’ve been going over all the workflows and can’t find a reason for the errors.

I think Bubble needs to invest in an easier email integration if they want to advertise this as a No Code. Fo email you need a engineering degree.

---

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 17, 2022, 11:11pm UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/2 "2022-12-17T23:11:39Z")

</div>

Hi @eric10,

What exactly is the issue? Are you seeing any errors for specific types of emails being sent?

Are you noticing that emails you expect to be sent aren’t showing up in the Postmark dashboard?

---

<div class="post-metadata">

**Author:** ![eric10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/eric10/32/111185_2.png) [@eric10](https://forum.bubble.io/u/eric10)\
**Post date:** [December 17, 2022, 11:48pm UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/3 "2022-12-17T23:48:19Z")

</div>

I’ve been sorting through trying to figure out what is failing.

I’m finding this error on some, so I’m not sure why this has started up again, since this was fixed in the past.

Workflow error - The service Postmark - notifications - Social Post Comment just returned an error (HTTP 422). Please consult their documentation to ensure your call is setup properly. Raw error: {"ErrorCode":402,"Message":"Received invalid JSON input."}

Which makes me think it’s something with this specific email/user. I’ve not been able to find any issues. Again this was working, so not sure why all of a sudden it’s not.

In the screen shot in the pink boxes are some things to note. The image has double “https”, but that should not stop the email. I also don’t know why the image addresses can’t be the same causing some having a “https”, and others not.

This is just one of the errors. the bigger error for me are the event reminder emails. again I get an invalid JSON input error, but can’t see what’s wrong with it.

 ![Screenshot 2022-12-17 at 3.26.12 PM](https://us1.discourse-cdn.com/bubble/original/3X/1/c/1cbbb114ee03811ad7511c45f1c1561d722c7a15.png)

---

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 17, 2022, 11:50pm UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/4 "2022-12-17T23:50:29Z")

</div>

Hey @eric10,

This screenshot is helpful to debug a little.

What does your WF setup look like when sending emails? The first potential issue I see is in the “subject” field. Why? Because it uses quotes and JSON doesn’t like quotes that aren’t escaped.

In that case, the fix would to use the `:formatted as JSON-safe` operator to escape any non-JSON safe characters.

* * *

> [@eric10](#):
>
> In the screen shot in the pink boxes are some things to note. The image has double “https”, but that should not stop the email. I also don’t know why the image addresses can’t be the same causing some having a “https”, and others not.

Yup, I agree with you on this. The extra `https` **isn’t** causing this issue

---

<div class="post-metadata">

**Author:** ![eric10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/eric10/32/111185_2.png) [@eric10](https://forum.bubble.io/u/eric10)\
**Post date:** [December 18, 2022, 12:08am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/5 "2022-12-18T00:08:42Z")

</div>

I thought I had all those set for JSON, so I updated that one, and updated the API Connector Pluging to remove the quotation marks from the code.

Here is another one from yesterday for my event reminder emails. I got the same warning, but I don’t think I saved the log entry and I only have 24 hours worth of logs.

Here are the workflows though.

 ![Screenshot 2022-12-17 at 4.06.41 PM](https://us1.discourse-cdn.com/bubble/original/3X/8/9/89cf1514aab9e2749df929e49794b967785681a5.png)

---

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 18, 2022, 12:12am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/6 "2022-12-18T00:12:24Z")

</div>

Hi @eric10,

The setup looks good. Can you see if you can pull from the logs what JSON content is actually being sent to Postmark? That way, you can paste the request into [jsonlint](https://jsonlint.com/) to help identify what exactly is causing the issues.

---

<div class="post-metadata">

**Author:** ![eric10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/eric10/32/111185_2.png) [@eric10](https://forum.bubble.io/u/eric10)\
**Post date:** [December 18, 2022, 12:13am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/7 "2022-12-18T00:13:53Z")

</div>

I’m setting up a reminder to be sent at 4:15. Once it sends I’ll post the error log.

By the way… what is this JSONlint you speak of??? I wish I knew of this earlier. haha

---

<div class="post-metadata">

**Author:** ![eric10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/eric10/32/111185_2.png) [@eric10](https://forum.bubble.io/u/eric10)\
**Post date:** [December 18, 2022, 12:17am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/8 "2022-12-18T00:17:52Z")

</div>

Here is the error log.

 ![Screenshot 2022-12-17 at 4.17.21 PM](https://us1.discourse-cdn.com/bubble/original/3X/a/0/a0fee255093f0df63d5296dcb830f33730475889.png)

---

<div class="post-metadata">

**Author:** ![eric10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/eric10/32/111185_2.png) [@eric10](https://forum.bubble.io/u/eric10)\
**Post date:** [December 18, 2022, 12:22am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/9 "2022-12-18T00:22:02Z")

</div>

I wonder if it’s the title?

The JSON formatting only adds to the dynamic data, so instead of being around everything it’s only around the event name.

---

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 18, 2022, 12:22am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/10 "2022-12-18T00:22:07Z")

</div>

Ah… I think I might see where the issue is.

For “event title,” put that expression in as Arbitrary text and remove JSON safe from `event's event_title` because you have some static text, then format the Arbitrary text as JSON-safe

---

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 18, 2022, 12:22am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/11 "2022-12-18T00:22:18Z")

</div>

Yep! Exactly what I was thinking 😊

---

<div class="post-metadata">

**Author:** ![eric10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/eric10/32/111185_2.png) [@eric10](https://forum.bubble.io/u/eric10)\
**Post date:** [December 18, 2022, 12:23am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/12 "2022-12-18T00:23:58Z")

</div>

Thank you for your help on this. I’m sure this will fix it. This is what I hate about how delicate this all is. The smallest thing will cause a mess. haha

---

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 18, 2022, 12:24am UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/13 "2022-12-18T00:24:36Z")

</div>

Yep, no problem! Anything JSON, really 😅

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/bubble/original/3X/2/8/2847faa74692c2ffa5d939d3dc3724cdd060d247.png) [@system](https://forum.bubble.io/u/system)\
**Post date:** [February 25, 2023, 11:07pm UTC](https://forum.bubble.io/t/some-emails-through-postmark-are-not-working-after-working-fine-for-months/237531/14 "2023-02-25T23:07:56Z")

</div>

Closed on February 25, 2023, 11:07pm UTC

This topic was automatically closed after 70 days. New replies are no longer allowed.
