# Logstash Elapsed filter 3.0.2 expired event issue

**URL:** <https://discuss.elastic.co/t/logstash-elapsed-filter-3-0-2-expired-event-issue/50204>\
**Category:** Logstash\
**Created:** [May 17, 2016, 9:56am UTC](https://discuss.elastic.co/t/logstash-elapsed-filter-3-0-2-expired-event-issue/50204 "2016-05-17T09:56:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hirakj](https://avatars.discourse-cdn.com/v4/letter/h/f4b2a3/32.png) [@hirakj](https://discuss.elastic.co/u/hirakj)\
**Post date:** [May 17, 2016, 9:56am UTC](https://discuss.elastic.co/t/logstash-elapsed-filter-3-0-2-expired-event-issue/50204/1 "2016-05-17T09:56:16Z")

</div>

Hello,

I have been using the elapsed filter on version 3.0.2.  
Elapsed filter doesn't seem to generate an expired event. Is there a new configuration for the filter I'm not seeing or is this a bug?

I'm running on a windows platform.

Below is the sample code:  
elapsed {  
start\_tag =\> "taskStarted"  
end\_tag =\> "taskTerminated"  
unique\_id\_field =\> "priceid"  
timeout =\> 10  
}

Thanks

---

<div class="post-metadata">

**Author:** ![pantheo](https://avatars.discourse-cdn.com/v4/letter/p/9de0a6/32.png) [@pantheo](https://discuss.elastic.co/u/pantheo)\
**Post date:** [June 22, 2016, 9:13am UTC](https://discuss.elastic.co/t/logstash-elapsed-filter-3-0-2-expired-event-issue/50204/2 "2016-06-22T09:13:50Z")

</div>

Try adding the **periodic\_flush =\> true** setting.  
That worked for me.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:51am UTC](https://discuss.elastic.co/t/logstash-elapsed-filter-3-0-2-expired-event-issue/50204/3 "2017-07-06T04:51:16Z")

</div>