---
title: Step 6: (Optional) Update an Application Version
slug: edgemanager/how-to-guides/lem-user-ui-guides/update-an-application-version
description: Learn how to update an application version.
docTags: 
createdAt: 2024-05-07T19:31:58.881Z
---

You can update an application version in the Primary marketplace catalog and initiate a sync from the Secondary marketplace catalog to pull the new changes.

# Before You Begin

- Make sure to finish *Steps 1 - Step 5 *of [Deploy Edge Applications to Multiple Sites Using Marketplace Catalog Sync](docId\:Z8R_5mVU1pezFXVSeNhQu) before proceeding.

# Step 6a: Add New Application Release Version in Primary Catalog

 **To add a new application release version in the primary catalog:**

1. Go to the *Primary* marketplace catalog you created in [Step 1: Create Primary Catalog With List of Applications](docId\:qBOZmPgvAQv8-_JM5vYv_) and select *Analytics* application to add a new release version.
   ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/HqO0-MmSUO3Pvmcq26X97_image.png "Primary marketplace catalog pane")
2. Click the **+** icon to open the *Add Release *dialog box.
   - Enter a suitable **name** for the release.
   - Enter a **description **for the release version.
   - Enter a **readme **for the release version.
   - Click **Save**.
     ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/kNACPo32IXVUD6Fl8Y55O_image.png" size="80" width="713" height="347" position="center" caption="Add Release dialog box" showCaption="true"}
3. You can add launch variables or docker container configurations to the draft application release. See *Step 3-Step 5* in [Add a Draft Application Release](docId\:pujQCF4jL0dUe8XjHsjmZ).

:::hint{type="info"}
**Note: **A Docker application release is always in one of two states: `RELEASED` (submitted) or `DRAFT`. When a Docker application release is in a `RELEASED` state, it cannot be further modified. Likewise, when it is in `DRAFT`, it can be modified.
:::

In this guide and in real-world settings, it is recommended that the secondary site always syncs to the draft application release to allow for further modifications specific to their site needs.

# Step 6b: Synchronize the Secondary Catalog to the Primary Catalog

Once the primary site (Canada) uploads the new version of the application into the Primary Catalog, the secondary site (Japan) manually initiates a sync with the primary catalog to pull the new application version.

**To synchronize the secondary catalog with the primary catalog using the new application release version:**

1. From the secondary marketplace catalog's *Synchronization* page, navigate to the **Synchronization: Secondary Catalog **pane.
2. Click **Sync **to pull the new version updates in the catalog.
   ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/BCZ6ACrG-HdZg3yXU8rfC_image.png "Synchronization page")

:::hint{type="info"}
**Note:** There is no need for approval of a primary catalog sync request this time. A secure connection has been established using a bootstrap file in [Step 3: Establish Secure Connection Between Primary and Secondary Catalog](docId\:s8JGesiGUpFPEHtDB_cfv).
:::

To verify if the application(s) have received the new release version, go to the **Applications **pane in the *Secondary *marketplace catalog and confirm the release update.

![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/X9doG39HYGY0VEdTprxxG_image.png "Secondary marketplace catalog: Applications pane")

:::hint{type="info"}
**Note: **To make changes to the pulled release version before deploying it to the edge device, see [Manage Application Releases](docId\:FoZMtmXkxEI6Y-gPZAEvg).
:::