# Alert triggering and ignoring filters

**URL:** <https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340>\
**Category:** Observability & Evals\
**Created:** [November 25, 2025, 4:15pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340 "2025-11-25T16:15:06Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidfanggg](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/davidfanggg/32/1735_2.png) [@davidfanggg](https://forum.langchain.com/u/davidfanggg)\
**Post date:** [November 25, 2025, 4:15pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/1 "2025-11-25T16:15:06Z")

</div>

Hi,

We are configuring LangSmith Alerts to trigger based on a specific error threshold, filtered by error message.

However, we are receiving notifications when we shouldn’t. It seems the alert is not filtering errors correctly.

When setting up the alert, the simulation graph reflects the correct behavior: we can clearly see the difference in values when the filter is applied versus when it isn’t. But once the alert is enabled, it appears that the filter is not being applied properly.

Any ideas?

---

<div class="post-metadata">

**Author:** ![arian](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@arian](https://forum.langchain.com/u/arian)\
**Post date:** [November 25, 2025, 9:28pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/2 "2025-11-25T21:28:53Z")

</div>

I’d like to investigate this - can you message me your organization id or workspace id? You can access them by clicking on Settings in the sidebar then clicking one of these buttons:

 ![image](https://canada1.discourse-cdn.com/flex007/uploads/langchain/original/2X/8/8b6f9eee0cf9666d2e7f81f8de7fe734ff299bbf.png)

---

<div class="post-metadata">

**Author:** ![davidfanggg](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/davidfanggg/32/1735_2.png) [@davidfanggg](https://forum.langchain.com/u/davidfanggg)\
**Post date:** [November 26, 2025, 9:18am UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/3 "2025-11-26T09:18:27Z")

</div>

Hi Arian, thanks for looking into it.

Workspace ID is 68c9ba3b-7f66-42fd-99b3-7167fa082003

---

<div class="post-metadata">

**Author:** ![arian](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@arian](https://forum.langchain.com/u/arian)\
**Post date:** [November 26, 2025, 7:50pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/4 "2025-11-26T19:50:31Z")

</div>

Great, thank you! Was able to repro and root cause. Fix should be shipping later today, will comment here when it’s live.

edit: I pushed an update - there was an issue with text normalization being inconsistently applied for the `contains`/`does not contain` filters. Please let me know if you still see your alert getting triggered incorrectly.

---

<div class="post-metadata">

**Author:** ![davidfanggg](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/davidfanggg/32/1735_2.png) [@davidfanggg](https://forum.langchain.com/u/davidfanggg)\
**Post date:** [December 1, 2025, 12:02pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/5 "2025-12-01T12:02:14Z")

</div>

Hi Arian,

Thanks for looking into it. We are still experiencing the issue.

---

<div class="post-metadata">

**Author:** ![arian](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@arian](https://forum.langchain.com/u/arian)\
**Post date:** [December 1, 2025, 4:04pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/6 "2025-12-01T16:04:53Z")

</div>

Sorry to hear that - I will continue investigating this issue today.

---

<div class="post-metadata">

**Author:** ![davidfanggg](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/davidfanggg/32/1735_2.png) [@davidfanggg](https://forum.langchain.com/u/davidfanggg)\
**Post date:** [December 2, 2025, 2:22pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/7 "2025-12-02T14:22:49Z")

</div>

One detail that might help to debug: the error message has multiple lines

![image.png](https://mail.google.com/mail/u/2?ui=2&ik=e1ca403954&attid=0.4&permmsgid=msg-a:r-1424886202369267309&th=19ade44af354a870&view=fimg&fur=ip&permmsgid=msg-a:r-1424886202369267309&sz=s0-l75-ft&attbid=ANGjdJ9jzVzWg7T6hEW96O2JgaaxxRH3t5C0MYzjrBg4sGUMhaW_5WbamVGBK2asRGOii90kFKQd2FmGYpawRohJ-blaZpmqIwEbBTbltmuF0WkVgswyy1TCDsKbnkQ&disp=emb&realattid=ii_miocaxvk3&zw)

And we are filtering by “Error: Abort”

Best regards,

David

---

<div class="post-metadata">

**Author:** ![davidfanggg](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/davidfanggg/32/1735_2.png) [@davidfanggg](https://forum.langchain.com/u/davidfanggg)\
**Post date:** [December 2, 2025, 2:31pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/8 "2025-12-02T14:31:52Z")

</div>

We noticed that just filtering by “Abort”, the alert filters correctly and doesnt’ trigger.

If the filter for “does not contain” is “Error: Abort”, then the filtering fails.

---

<div class="post-metadata">

**Author:** ![arian](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@arian](https://forum.langchain.com/u/arian)\
**Post date:** [December 2, 2025, 6:22pm UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/9 "2025-12-02T18:22:01Z")

</div>

I am seeing some abort related errors on your runs that would get properly filtered by just “Abort” but not “Error: Abort” e.g.

`This operation was aborted`  
`AbortError: This operation was aborted`  
`... stacktrace ...`

which would explain what you are encountering.

---

<div class="post-metadata">

**Author:** ![davidfanggg](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/davidfanggg/32/1735_2.png) [@davidfanggg](https://forum.langchain.com/u/davidfanggg)\
**Post date:** [April 29, 2026, 10:37am UTC](https://forum.langchain.com/t/alert-triggering-and-ignoring-filters/2340/10 "2026-04-29T10:37:54Z")

</div>

Hi @arian , hope you are doing well. We are experiencing a similar issue now but with a metadata filter. We have an alert filter with `metadata.ls_run_depth = 0`, but we are getting falsely alerted for errors without this metadata value. Would you be able to take a look?

 ![image](https://canada1.discourse-cdn.com/flex007/uploads/langchain/original/2X/7/77544992fc78b14a52c55ebb8a39a89a3d296d64.png)
