Components Version Update

This documentation is valid for:

This log shows the version updates of the components added to the platform.

2026

January 14

RAG_IMAGE_VERSION=1.0.43
SAIA_CORE_IMAGE_VERSION=1.1.5768-hf-18.14-75
SAIA_EVAL_IMAGE_VERSION=1.1.111-qa-mysql
OMNI_PARSER_IMAGE_VERSION=1.0.31
CHAT_V2_FRONTEND_IMAGE_VERSION=v20260108-01-frontend-976ef98f
CHAT_V2_BACKEND_IMAGE_VERSION=v20260114-03-backend-b2b3f5dc
AGENT_STUDIO_IMAGE_VERSION=v20260108-01-agentstudio-976ef98f
DATA_ANALYST_IMAGE_VERSION=2.1.62-data-analyst-qa
FROID_B_IMAGE_VERSION=2.1.103-froidb
SAIA_LLM_SERVER_IMAGE_VERSION=1.0.96
AGENT_TOOLS_VERSION=1.0.250-backend
AI_STATION_FRONTEND_IMAGE_VERSION=2.2.1029-aistation-qa-53cf49ee
KEYCLOAK_TENANT_IMAGE_VERSION=v25.0.5
FLUENTLAB_IMAGE_VERSION=2.6.0-SNAPSHOT.980.bf6f2b2

Required Manual Steps

Data migration (normalize file references in existing conversations)
- This migration updates existing conversation messages to use normalized file references.
- A Super Admin must run it manually from the Console > System > Metadata > AI Station > Conversation Message File FileId Fix > Apply FileId Fix > Click Confirm.
- To review results, go to System > Operation Logs.
- Notes:
  - The migration only applies to existing file references. It does not apply to temporary files.
  - The log can show files not found. This does not necessarily indicate a problem if those references no longer exist.
  - The process runs in a submitted thread, so it is not a deployment prerequisite and you do not need to wait for it to finish.
Verify Japanese characters (System module revision 27)
- After updating the System module to revision 27, verify the BACKOFFICE_AVAILABLE_LANGUAGES parameter to ensure Japanese characters display correctly.
- If the parameter already existed before the update, no action is required because the update does not overwrite it.
- If the parameter was introduced with revision 27, update the Japanese entry as follows:
  Replace:
  {"name":"Japanese","iso_code_6391":"ja","description":"???"},
  With:
  {"name":"Japanese","iso_code_6391":"ja","description":"日本語"},
  This issue occurs because special characters are not mapped correctly in the DataProvider where the parameter is defined.
Cost recalculation in Requests (from December 1, 2025)
- Recalculate request costs starting on December 1, 2025 for the following models:
  - gpt-5-codex
  - gpt-5-chat-latest
  - gpt-5.1-codex-max
  - gpt-5-pro
  - gpt-5.2-pro
- You must complete two stages:
  - Stage 1: Recalculate costs for each model
    1. Go to Console > System > Metadata > Request utils > Request cost recalculation.
    2. Set From to December 1, 2025.
    3. Set To to the current date.
    4. In Request AIModel Name, enter one model from the list above.
    5. Click EXECUTE COST RECALCULATION (SUBMIT).
    6. Check results in System > Operation Logs.
      This process runs in a submitted thread.
      Repeat steps 6 to 7 five times, once per model.
  - Stage 2: Update dashboard summary data
    1. Go to Console > System > Metadata > Request utils > Reprocess Requests and load summary table.
    2. Click Load a specific period.
    3. Enter December 1, 2025 as the start date and the current date as the end date.
    4. Click REPROCESS REQUESTS (SUBMIT).
    5. Check results in System > Operation Logs.
      This process also runs in a submitted thread.

January 5

RAG_IMAGE_VERSION=1.0.40
SAIA_CORE_IMAGE_VERSION=1.1.5602-hf-18.14-56
SAIA_EVAL_IMAGE_VERSION=1.1.111-qa-mysql
OMNI_PARSER_IMAGE_VERSION=1.0.31
CHAT_V2_FRONTEND_IMAGE_VERSION=v20251226-02-frontend-b30a83b6
CHAT_V2_BACKEND_IMAGE_VERSION=v20251219-02-backend-d98c5461
AGENT_STUDIO_IMAGE_VERSION=v20251219-02-agentstudio-3f0b8a69
DATA_ANALYST_IMAGE_VERSION=2.1.62-data-analyst-qa
FROID_B_IMAGE_VERSION=2.1.103-froidb
SAIA_LLM_SERVER_IMAGE_VERSION=1.0.87
AGENT_TOOLS_VERSION=1.0.250-backend
AI_STATION_FRONTEND_IMAGE_VERSION=2.2.926-aistation-qa-9654a655
KEYCLOAK_TENANT_IMAGE_VERSION=v25.0.5
FLUENTLAB_IMAGE_VERSION=2.6.0-SNAPSHOT.980.bf6f2b2

Required Manual Steps

No manual steps required. This change permits proper configuration of INSTALLATION_CONFIG_PROVIDER=geai for the Workspace when set.

2025

December 23

RAG_IMAGE_VERSION=1.0.40
SAIA_CORE_IMAGE_VERSION=1.1.5602-hf-18.14-56
SAIA_EVAL_IMAGE_VERSION=1.1.111-qa-mysql
OMNI_PARSER_IMAGE_VERSION=1.0.31
CHAT_V2_FRONTEND_IMAGE_VERSION=2.2.918-frontend-qa-b4c4cafe
CHAT_V2_BACKEND_IMAGE_VERSION=v20251219-02-backend-d98c5461
AGENT_STUDIO_IMAGE_VERSION=v20251219-02-agentstudio-3f0b8a69
DATA_ANALYST_IMAGE_VERSION=2.1.62-data-analyst-qa
FROID_B_IMAGE_VERSION=2.1.103-froidb
SAIA_LLM_SERVER_IMAGE_VERSION=1.0.87
AGENT_TOOLS_VERSION=1.0.250-backend
AI_STATION_FRONTEND_IMAGE_VERSION=2.2.926-aistation-qa-9654a655
KEYCLOAK_TENANT_IMAGE_VERSION=v25.0.5
FLUENTLAB_IMAGE_VERSION=2.6.0-SNAPSHOT.980.bf6f2b2

Required Manual Steps

Flows SSO
In GAM UI go to Applications > Fluentlab.
- Edit the configuration to add:
  - Additional user scopes: openid
Flows SSO in SaaS for clients with custom IdP and subdomain
- This is only for clients using the SaaS with their own IdP for login and custom subdomain.
- Assuming that the client is already setup to access Flow from GEAI Console.
- Go to Console > System > Parameters.
- Look for the client Organization.
- Edit the parameter UIConfiguration.
- In the JSON (Value S), under the customization attribute, add a new property called flows with the following content:

{
   ...
   "customization": {
      ...
      "flows": {
         "idp": ""
      }
   }
}

The client IdP should match with the one defined in the Keycloak from Flows.

December 12

RAG_IMAGE_VERSION=1.0.40
SAIA_CORE_IMAGE_VERSION=1.1.5527-hf-18.14-50
SAIA_EVAL_IMAGE_VERSION=1.1.111-qa-mysql
OMNI_PARSER_IMAGE_VERSION=1.0.31
CHAT_V2_FRONTEND_IMAGE_VERSION=2.2.918-frontend-qa-b4c4cafe
CHAT_V2_BACKEND_IMAGE_VERSION=2.2.918-backend-qa-b4c4cafe
AGENT_STUDIO_IMAGE_VERSION=2.2.918-agentstudio-qa-b4c4cafe
DATA_ANALYST_IMAGE_VERSION=2.1.62-data-analyst-qa
FROID_B_IMAGE_VERSION=2.1.103-froidb
SAIA_LLM_SERVER_IMAGE_VERSION=1.0.77
AGENT_TOOLS_VERSION=1.0.250-backend
AI_STATION_FRONTEND_IMAGE_VERSION=2.2.926-aistation-qa-9654a655
KEYCLOAK_TENANT_IMAGE_VERSION=v25.0.5
FLUENTLAB_IMAGE_VERSION=2.6.0-SNAPSHOT.980.bf6f2b2

Required Manual Steps

Reinstall system module “The Lab Public Components” to update Iris definition
- Go to Console > System > System Modules
- Search for “The Lab Public Components”
- Click REINSTALL/UPDATE
- Do the same for Module: “The Lab Tools: Google Drive Tools”
Configuration for Lab, Station and Workspace
- The following configuration apply to the new header menu and help menu options.
- Define the following environment variable for Lab, Station and Workspace backends: INSTALLATION_CONFIG_PROVIDER=geai.
  - This defines that the next UIConfiguration parameter will be used to load the configuration defined in it.
- Go to Console > System > Parameters
- Create a new parameter called UIConfiguration with the following content:

{
  "configurationDomain": "<tenant_domain>",
  "gamAuthTypes": [
    "<authentication_name>"    
  ],
  "customization": {
    "applicationsUrl": {
      "station": "<station_url>",
      "console": "<console_url>",
      "lab": "<lab_url>",
      "workspace": "<workspace_url>"
    },
    "support": {
      "contactUs": "<contact_us_url>",
      "helpUrl": "https://docs.globant.ai",
      "tutorialVideo": "https://www.youtube.com/embed/0eXMmPRGXS4"
    }
  }
}

Where:

<tenant_domain>: domain where the workspace is running, for example, customer-workspace.domain.com
gamAuthTypes is a list of Authentication name defined in the Security configuration.
<contact_us_url>: for example mailto:support@domain.com
Check that the parameter has the scope on System in Advance section
Also for the Station and Workspace you need to set this environment variables in the frontend containers:
- VITE_GEAI_STATION_URL_VALUE=<station_url>
- VITE_GEAI_LAB_URL_VALUE=<laburl>
- VITE_GEAI_WORKSPACE_URL_VALUE=<workspaceurl>
- VITE_GEAI_CONSOLE_URL_VALUE=<consoleurl>

December 1

RAG_IMAGE_VERSION=1.0.40
SAIA_CORE_IMAGE_VERSION=1.1.5441-qa-18.14-305
SAIA_EVAL_IMAGE_VERSION=1.1.111-qa-mysql
OMNI_PARSER_IMAGE_VERSION=1.0.31
CHAT_V2_FRONTEND_IMAGE_VERSION=2.2.918-frontend-qa-b4c4cafe
CHAT_V2_BACKEND_IMAGE_VERSION=2.2.918-backend-qa-b4c4cafe
AGENT_STUDIO_IMAGE_VERSION=2.2.918-agentstudio-qa-b4c4cafe
DATA_ANALYST_IMAGE_VERSION=2.1.62-data-analyst-qa
FROID_B_IMAGE_VERSION=2.1.103-froidb
SAIA_LLM_SERVER_IMAGE_VERSION=1.0.77
AGENT_TOOLS_VERSION=1.0.250-backend
AI_STATION_FRONTEND_IMAGE_VERSION=2.2.918-aistation-qa-b4c4cafe
AI_STATION_REACT_FRONTEND_IMAGE_VERSION=2.2.808-aistation-react-qa-c08dd1a6
KEYCLOAK_TENANT_IMAGE_VERSION=v25.0.5
FLUENTLAB_IMAGE_VERSION=2.6.0-SNAPSHOT.980.bf6f2b2

Breaking Changes

geai-aistudio-frontend container now responds in port 8080.
- If not changed, health check will fail
Azure Environments
- It is mandatory to Add the following EnvVariable to the API and Console containers GEAI_JVM_MAXRAM=0