Yes I got you problem, as a workaround you can definitely create another key called for example < time >_expire and set expiration on it. Then you need to register on changes on this key and you will get the expire event. Its not the best solution but it will work (notice that there might be a little delay in the expire event because expiration is lazy so you will get it on the cron job of redis). I do plan to support timer like api in future gears releases.