# using &\*\_expire with interval values defined before

**URL:** <https://community.zeek.org/t/using-expire-with-interval-values-defined-before/685>\
**Category:** Zeek\
**Created:** [February 6, 2005, 12:45am UTC](https://community.zeek.org/t/using-expire-with-interval-values-defined-before/685 "2005-02-06T00:45:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vern](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/vern/32/630_2.png) [@Vern](https://community.zeek.org/u/Vern)\
**Post date:** [February 6, 2005, 12:45am UTC](https://community.zeek.org/t/using-expire-with-interval-values-defined-before/685/1 "2005-02-06T00:45:54Z")

</div>

> does anyone know why this doesn't work and results in an error?
> 
> policy-script:  
> \> const tcp\_scan\_period = 2 min &redef;  
> \> global tcp\_scan: table[addr] of count &write\_expire=tcp\_scan\_period;
> 
> error:  
> \> line xx (tcp\_scan\_period): bad tag in ExprVal::Val

Definitely a bug. I'm able to reproduce it and will include a fix with  
the next release (which has been delayed due to some other late-breaking  
bugs, sigh).

By the way, any time you see "bad tag", it's definitely a bug, that's  
an internal error message.

&nbsp;&nbsp;&nbsp;&nbsp;Vern

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:37pm UTC](https://community.zeek.org/t/using-expire-with-interval-values-defined-before/685/2 "2022-05-06T15:37:20Z")

</div>