# Pipeline Drop Message Not Working

**URL:** <https://community.graylog.org/t/pipeline-drop-message-not-working/27261>\
**Category:** Graylog Central (peer support)\
**Created:** [January 12, 2023, 8:02pm UTC](https://community.graylog.org/t/pipeline-drop-message-not-working/27261 "2023-01-12T20:02:27Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![gsmith](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gsmith/32/1222_2.png) [@gsmith](https://community.graylog.org/u/gsmith)\
**Post date:** [January 18, 2023, 4:55am UTC](https://community.graylog.org/t/pipeline-drop-message-not-working/27261/13 "2023-01-18T04:55:28Z")

</div>

Hey @bluescreenofwin

Not sure whats going on with dropping a message, and not sure if you seen this.

> [@Unable to Drop syslog messages based on message contents](https://community.graylog.org/t/unable-to-drop-syslog-messages-based-on-message-contents/25242):
>
> HI All, I am encountering an issue with pipeline configuration where I seem to be unable to drop Syslog messages based on the message contents. I have done some googling / searching of the forum and the other suggestions don’t seem to be helping. I am running Graylog 4.1.14-1 on Ubuntu 22.04.1 LTS An example of the message type I am trying to drop is below: %CDP-4-DUPLEX\_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/32 (not half duplex), with -Device Name- GigabitEthernet0 (hal…

Kind of looks like you issue

---

_[View the full topic](https://community.graylog.org/t/pipeline-drop-message-not-working/27261)._