---
title: "Backwards Compatibility by Release"
slug: "xa-backwards-compatibility-by-release"
updated: 2026-03-05T22:05:14Z
published: 2026-03-05T22:05:14Z
canonical: "healthcare.rapididentity.com/xa-backwards-compatibility-by-release"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://healthcare.rapididentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Backwards Compatibility by Release

In most instances, an older version of the XA Client or Server will continue to function with a newer version. However, additional features provided by the newer release may not fully function as intended.

If you begin to experience issues with either the client or server after an upgrade, we encourage that you upgrade the other to the matching version of XA and see if the issue(s) persist.

ℹ️ Compatibility Example

The HCIDeploy Publisher management application and XA Toolbar must always match the major server version they manage. Tools from 4.10 and earlier cannot manage a 4.11 or higher server, and tools from 4.11 cannot manage a 4.10 server.

For example, a 4.10 HCIDeploy Publisher or XA Toolbar cannot be pointed at a 4.11 server; it must remain connected to a 4.10 server. Likewise, 4.11 management tools require a 4.11 or higher server. While a 4.10 client may still pull updates from a 4.11 server, it cannot be managed by newer tools, and older 4.10 tools cannot maintain a 4.11 server.

## XA Server

**Backwards Compatible Client Versions** All XA Server 4.x version are backwards compatible with the following client versions:

- 4.14
- 4.13
- 4.12
- 4.11

---

## XA Client

**Backwards Compatible Server Versions** All XA Client 4.x version are backwards compatible with the following server versions:

- 4.14
- 4.13
- 4.12
- 4.11