Conversations in TOCK are only valid for a certain duration, yet the frontend history never expires. For end users, this can lead to the impression that an old conversation can be simply resumed when that is not the case.

It would be practical to have a configuration property for history max age, which could for example mirror the tock_web_cookie_auth_max_age property in the backend.