> For the complete documentation index, see [llms.txt](https://docs.helvia.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helvia.ai/resources/release-notes/helvia.ai-release-2026.07.29.md).
# Helvia.ai Release 2026.07.29
## 1. Shared Variables And Contains Filters Across The Observatory
The Observatory filter row gains two shared filters in this release: **Variables** and **Contains**. They join the existing shared **Tags** filter, so you set a filter once and it applies across every Observatory screen where it is relevant. The **Contains** filter combines five session criteria in one control: Default Fallback, User Feedback, Livechat, CSAT Response, and User Interaction.
**Why it matters:** Previously the five session criteria lived only on the Chat Sessions list, and there was no shared way to narrow by a specific variable. Moving between screens meant losing that context. Sharing these filters removes the repetition and keeps your view consistent as you move around.
**Example use case:** You want every session that triggered the default fallback and left CSAT feedback last week. You set the **Contains** filter to Default Fallback and CSAT Response once, then move across Chat Sessions, Analytics, and Interaction Logs with the same filter already applied, including in any export.
**How it works:** Set the **Variables** and **Contains** filters in the **Observatory** filter row. Selections persist in the URL so you can share a link, and they can be saved with your other filters. Subcategories that do not use a given filter keep your selection and ignore it until you return to a screen that does.
## 2. Run Automations On A Recurring Interval
Automations can now run on a recurring interval, such as every 5 minutes or every 90 minutes, as an alternative to fixed weekly scheduling. You choose the trigger mode when you create the Automation.
**Why it matters:** Weekly scheduling only supported fixed calendar slots, a specific day and time. Some Automations need to run on a steady cadence regardless of the day or the clock. Interval triggers add that option while leaving existing weekly Automations unchanged.
**Example use case:** You want an Automation that checks for new records and pushes updates every 15 minutes throughout the day. You create the Automation, choose the interval mode, and set the interval to 15 minutes. It runs on that cadence continuously, with no need to define individual time slots.
**How it works:** When you create an Automation, choose the schedule mode: weekly (day and time, as before) or interval (every X minutes). The interval accepts whole minutes with a minimum of 1. The mode is fixed once the Automation is created, so to switch modes you delete and recreate it. Firing cadence is approximate rather than exact to the second.
## 3. Clearer Agent Sidebar With A New Privacy & Security Menu
The Agent sidebar gains a dedicated **Privacy & Security** section that groups the controls for protecting and governing your data in one place. It sits between **Automations** and **Backups**.
**Why it matters:** Authentication settings and privacy controls used to live in separate places in the sidebar, which made them harder to find. Grouping them under one parent gives you a clearer path to the settings that govern access and data handling.
**Example use case:** You need to review your Agent's data retention and anonymization rules, then check its authentication configuration. Both now sit under **Privacy & Security**, so you handle them without hunting across the sidebar.
**How it works:** Open the Agent sidebar and go to **Privacy & Security**. It contains two items: **Authentication** for JWT and OIDC configuration, available to admins, and **Anonymization** for anonymization, obfuscation, and data-retention controls, visible to everyone and read-only for non-admins. The **Settings** menu now opens **Configuration** directly.
