# My email notification was garbled and came in fine after a retry. Why did it fail the first time?

**URL:** <https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830>\
**Category:** Help and Support\
**Tags:** notifications\
**Created:** [December 8, 2025, 6:32am UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830 "2025-12-08T06:32:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![finrepyash](https://forums.distill.io/letter_avatar_proxy/v4/letter/f/b5e925/32.png) [@finrepyash](https://forums.distill.io/u/finrepyash)\
**Post date:** [December 8, 2025, 6:32am UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830/1 "2025-12-08T06:32:22Z")

</div>

Hi

There was an alert on 4th December for one of my monitors. The email alert that I got looks as per the screenshot below:

 ![Screenshot 2025-12-08 at 11.56.31 AM](https://forums.distill.io/uploads/default/original/2X/4/42ac67c0ff55991f4494c7d5515d6c3cf3eb48fc.png)

I went in the diff alert on my Watchlist, on the specific change, and retriggered the email. The new email that I got looked fine and as per expectations.

Why did it fail the first time? How can it be avoided, or auto-recovered (I don’t mind two alerts - one faulty and one recovered.

---

<div class="post-metadata">

**Author:** ![srijith](https://forums.distill.io/letter_avatar_proxy/v4/letter/s/c77e96/32.png) [@srijith](https://forums.distill.io/u/srijith)\
**Post date:** [December 8, 2025, 10:34am UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830/2 "2025-12-08T10:34:46Z")

</div>

@finrepyash From what you’ve described and the image provided, it looks like the initial alert captured **garbled data** rather than the expected content. This is usually caused by **dynamic content** , **cookie consent banners** , or other temporary overlays that load during the check — which can interfere with what the monitor captures.

Here are a few suggestions to improve reliability:

1. **Use the Visual Selector to target only the specific portion of the content you need.** Avoid selecting too broad an area or elements likely to change or be blocked dynamically. **Exclude cookie banners or dynamic overlays** from the selection

2. **Ensure cookies are accepted** on the page before setting up the monitor.

3. **Consider switching to a [Dedicated Cloud Device](https://distill.io/docs/web-monitor/dedicated-cloud-devices/#creating-a-dedicated-device)** for more consistent monitoring.

If you need help with the current monitor setup, please let us know.

---

<div class="post-metadata">

**Author:** ![finrepyash](https://forums.distill.io/letter_avatar_proxy/v4/letter/f/b5e925/32.png) [@finrepyash](https://forums.distill.io/u/finrepyash)\
**Post date:** [December 8, 2025, 12:14pm UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830/3 "2025-12-08T12:14:22Z")

</div>

@srijith thanks for this. I will try the third option since the first two are already satisfied. I was facing a time interval issue with another monitor, and am doing the same for all of the monitors to allow for loading. Will in parallel figure out the Dedicated Cloud Device setup and migrate the monitors to that.

---

<div class="post-metadata">

**Author:** ![finrepyash](https://forums.distill.io/letter_avatar_proxy/v4/letter/f/b5e925/32.png) [@finrepyash](https://forums.distill.io/u/finrepyash)\
**Post date:** [December 8, 2025, 2:39pm UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830/4 "2025-12-08T14:39:32Z")

</div>

Hi

I have a trigger set from which I got the email with the details of a diff on November 26, 10:25 am local time. The runs don’t show any diff detected in the history.

 ![Screenshot 2025-12-08 at 8.07.12 PM](https://forums.distill.io/uploads/default/original/2X/c/c3a459cc108794fdb0b8aaea5e3c020eab8ee6cc.png)

Am I missing something?

---

<div class="post-metadata">

**Author:** ![srijith](https://forums.distill.io/letter_avatar_proxy/v4/letter/s/c77e96/32.png) [@srijith](https://forums.distill.io/u/srijith)\
**Post date:** [December 9, 2025, 5:07am UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830/5 "2025-12-09T05:07:31Z")

</div>

> [@finrepyash](#):
>
> I have a trigger set from which I got the email with the details of a diff on November 26, 10:25 am local time. The runs don’t show any diff detected in the history.

@finrepyash It’s possible this might be a case of monitor mix-up — it can happen when there are multiple monitors with similar names. To help clarify, could you please check the following:

1. Visit your **Action Logs** here: [https://monitor.distill.io/#/u/0/usage/logs/](https://monitor.distill.io/#/u/0/usage/logs/) and check for the log with timestamp November 26 and action as Email. You can click on the monitor name and verify if its the same monitor.

2. Then, also **open the email alert** you received on November 26 and click on the **“Change History”** and check if that change belongs to the same monitor.

This should help ensure we’re looking at the same monitor and get to the bottom of the discrepancy.

---

<div class="post-metadata">

**Author:** ![srijith](https://forums.distill.io/letter_avatar_proxy/v4/letter/s/c77e96/32.png) [@srijith](https://forums.distill.io/u/srijith)\
**Post date:** [December 9, 2025, 6:16am UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830/6 "2025-12-09T06:16:10Z")

</div>

@finrepyash I also wanted to share one more possibility that might explain what you’re seeing.

If the monitor was running in the **cloud** at the time of the alert, please note that in the **free plan** , only the **last 3 versions** of change history are stored. So if there were additional changes after November 26, the older entry may have been automatically removed, which could be why you’re not seeing it in the monitor’s history now.

---

<div class="post-metadata">

**Author:** ![finrepyash](https://forums.distill.io/letter_avatar_proxy/v4/letter/f/b5e925/32.png) [@finrepyash](https://forums.distill.io/u/finrepyash)\
**Post date:** [December 12, 2025, 5:22am UTC](https://forums.distill.io/t/my-email-notification-was-garbled-and-came-in-fine-after-a-retry-why-did-it-fail-the-first-time/5830/7 "2025-12-12T05:22:03Z")

</div>

@srijith thanks, I think that is it. Thanks for clarifying
