# Events, alerts fired only after a second message arrives **URL:** \ **Category:** Graylog Central (peer support)\ **Tags:** pipeline-rules, route-to-streampl\ **Created:** [March 23, 2020, 9:30pm UTC](https://community.graylog.org/t/events-alerts-fired-only-after-a-second-message-arrives/14605 "2020-03-23T21:30:22Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![maxplay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/maxplay/32/6074_2.png) [@maxplay](https://community.graylog.org/u/maxplay)\ **Post date:** [March 24, 2020, 3:53pm UTC](https://community.graylog.org/t/events-alerts-fired-only-after-a-second-message-arrives/14605/4 "2020-03-24T15:53:29Z")
@jan **maybe** the problem here is also related to the one @DerBeton (found solution?) posted some days ago…they seem to be similar… > [@No Event / Alert fired](https://community.graylog.org/t/no-event-alert-fired/14391): > > Hey Graylog Community We have a one node Graylog Setup with Docker. Versions: graylog:3.2.2 mongo:3 elasticsearch-oss:6.8.5 Our environment has only 2 clients connected until now and our log rate is below 1 log/minute. We have an alert set up, which should be triggered as soon as a critical error enters graylog (Search every minute for 1 minute). The Problem is, that the event is only fired, when there is another event after the critical one. For now we solved the problem with a Random H… --- _[View the full topic](https://community.graylog.org/t/events-alerts-fired-only-after-a-second-message-arrives/14605)._