# 2025.22 Infrastructure Changes

### **🔄 GPT-4 End of Life & GPT-4o Model Upgrade**

**Important: GPT-4 and GPT-4-32k will reach end of life on June 6, 2025.**

**💡 What’s Changing**  
With **Release 22**, we are upgrading all GPT-4 models to **GPT-4o (AZURE_GPT_4o_2024_1120)** across both our:

- **Chat solution**
- **Recording solution**

This new model brings:

- **Swiss-based inference only**
- **Expanded context window** (128K tokens)
- **Higher throughput**
- **More verbose reports** (e.g., ending with “Do you want me to refine this?”)

**🚀 Upgrade Path**
- **If you deploy Release 22**:
    - The GPT-4o upgrade is applied **automatically** for both Chat and Recording.
- **If you do not deploy Release 22 by June 6**:
    - You must **manually switch** your GPT configuration to AZURE_GPT_4o_2024_1120
    - This applies to **both** Chat and Recording

> ⚠️ Not upgrading by June 6 may lead to **broken or unexpected behavior** in Unique’s chat and reporting.

📞 **Need help?** Contact Customer Success to configure GPT-4o manually or test the setup early.

* * *

### 📊 Analytics

#### 🚀 What’s Changing
Starting with **Release 22**, we’re rolling out the analytics improvements that were previously available in **Release 2025.16** as a beta feature. These enhancements are designed to provide greater stability when exporting analytics data and are now being made available to more users.

#### **Key Update:**
- In the **Chat Interactions Analytics**, the order of exported data in the CSV file has changed.
    - **Previously:** Data was sorted by the `Email` column.
    - **Now:** Data is sorted by the `Date` column.

#### 🔧 Feature Availability
- The feature flags for these improvements are now **enabled by default**. To configure this in your tenant, set this flags to be true  
    - `ENABLE_DOWNLOAD_UPLOAD_FILES_AS_STREAM`
    - `ENABLE_UPLOAD_CHAT_INTERACTIONS_AS_STREAM`
    - `ENABLE_ANALYTICS_CHAT_DETAILED_INTERACTIONS_PRISMA_CURSOR`
- In the **next release**, these improvements will become **Generally Available (GA)**, and the feature flags will be removed—making the functionality available to all users without additional configuration.

* * *

# Changes on Application environment

| **Change** | **Name** | **Default** | **Example** | **Required** | **Applications** | **Short Description** |
|------------|----------|-------------|-------------|--------------|-------------------|-----------------------|
| Added | `REBUILD_METADATA_WAIT_AFTER_TRESHOLD` | 40 | `40` | No | node-ingestion | This number determines how many contents should be processed before taking a pause (waiting) during metadata rebuilding operations. |
| Added | `REBUILD_METADATA_WAIT_IN_MS` | 250 | `250` | No | node-ingestion | This controls the duration of the pause/wait between metadata rebuilding batches. It is in milliseconds.<br>Together with `REBUILD_METADATA_WAIT_AFTER_TRESHOLD`, they work as rate-limit for the metadata rebuild process. |
| Added | `FEATURE_FLAG_CONFIGURE_FILE_METADATA_UN_10908` | `false` | `false` | No | next-knowledge-upload | Activates static metadata feature that allows admin to define static metadata in the UI that should be present on all files in the scope |
| _Changed_ | `ENABLE_DOWNLOAD_UPLOAD_FILES_AS_STREAM` | `