Hello, The DetectDuplicate processor takes a Cache Entry Identifier as the value that is cached, and the Age Off Duration specifies a TTL for that cache entry. What happens if that same CacheEntryIdentifier comes in a second time after the value is already cached - is the TTL now set at the TTL for the time the second entry was encountered, or does it remain at the TTL of the original entry? It seems from my testing that each time that Cache Entry Identifier is encountered, that TTL is reset to the latest entry. In this case, if I have the Age Off set to one hour, but I encounter this identifier multiple times an hour, the entry will never age off, since it is constantly being updated. I suppose I can solve this problem by prepending part of a date (like the date plus the hour) so that guarantees that at least once an hour I'll have a new entry. But this is an imperfect solution. Is there a way to tell DetectDuplicate that if encounters a value already cached, that it should leave the original TTL in place? Thank you,Elli
