# Cache

These settings control how long Aisera retains context for interactive conversation elements after they are presented to the user. They affect how long users can return to and interact with buttons, forms, and other response elements before the associated context expires. When context expires, users receive a message indicating the conversation has ended and are prompted to start a new one.

### Follow Up Cache Expire in Hours

| **Type**    | Text field (integers) |
| ----------- | --------------------- |
| **Default** | `24`                  |

Controls how long Aisera retains the context associated with interactive response elements, such as buttons, question responses, and form steps, after they are presented to the user. This applies across all channels.

When a user interacts with a response element after the cache has expired, Aisera ends the conversation and sends the message: "We have finished this conversation. If you want to start a new conversation, please type your question." In email channels, expired interactions fail silently with no message sent to the user. The message shown to users in other channels is customizable via the `fail_to_continue_closed_conversation` message in Conversation Messages. See [Conversation Messages →](https://docs.aisera.com/aiseragpt/how-to-set-up-an-aiseragpt-bot/add-conversation-messages#to-edit-conversation-messages) for instructions on editing this message.

Increase this value when your users frequently delay responding to Aisera messages, such as in asynchronous channels where responses may not happen within the same session. There is no enforced maximum value.

See also: [Generic Event Follow Up Cache Expire In Hours](#generic-event-follow-up-cache-expire-in-hours), [Silent Cache Expire In Hours](#silent-cache-expire-in-hours)

### Generic Event Follow Up Cache Expire In Hours

| **Type**    | Text field (integers) |
| ----------- | --------------------- |
| **Default** | `48`                  |

Controls how long Aisera retains the context for action buttons delivered in outbound generic event notifications. When a user clicks a button after the cache has expired, Aisera ends the conversation and sends the configurable "conversation finished" message instead of executing the action.

The default of `48` hours is set higher than the standard Follow Up Cache Expire in Hours to account for delayed responses to proactive notifications.

Increase this value when users are likely to respond to notifications hours or days after delivery. The expiry message is customizable via the `fail_to_continue_closed_conversation` message in Conversation Messages. See [Conversation Messages →](https://docs.aisera.com/aiseragpt/how-to-set-up-an-aiseragpt-bot/add-conversation-messages#to-edit-conversation-messages) for instructions on editing this message.

See also: [Follow Up Cache Expire in Hours](#follow-up-cache-expire-in-hours), [Silent Cache Expire In Hours](#silent-cache-expire-in-hours)

### Silent Cache Expire In Hours

| **Type**    | Text field (integers) |
| ----------- | --------------------- |
| **Default** | `48`                  |

Controls how long Aisera retains the context needed to support live agent escalation after a conversation ends. When a user escalates to a live agent, Aisera caches the engagement context including channel information, the original request, and conversation ID. This context is required for routing the user to a live agent or associating a support ticket. If the cache expires before the escalation is processed, that context is no longer available.

Increase this value when escalations in your environment may occur significantly after the original conversation ends.

See also: [Follow Up Cache Expire in Hours](#follow-up-cache-expire-in-hours), [Generic Event Follow Up Cache Expire In Hours](#generic-event-follow-up-cache-expire-in-hours)