---
title: "Upgrading DataEngine Runtime Version"
slug: "how-to-upgrade-dataengine-runtime-en"
tags: ["5.4"]
updated: 2026-10-28T01:54:43Z
published: 2026-10-28T01:54:43Z
canonical: "docs.vastdata.com/how-to-upgrade-dataengine-runtime-en"
---

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

# Upgrading DataEngine Runtime Version

In the event that you need to upgrade DataEngine runtime, follow this procedure:

1. Run the [DataEngine CLI](https://github.com/vast-data/dataengine-cli), and make sure it is updated to the latest builder image:
  1. Use [vastde builders inspect](https://github.com/vast-data/dataengine-cli/blob/main/docs/references/commands/vastde_builders_inspect.md) to check current builder image URL:

```plaintext
user@user-machine:~$ vastde builders inspect
Current Builder Image Configuration

Builder Image URL: https://github.com/vast-data/dataengine-cli/releases/tag/v5.4.1-dev.29d4871e

To change the builder image, use: vastde builders set <image-url>
To view tag details, use: vastde builders inspect <tag>
```
  2. Run [vastde builders list](https://github.com/vast-data/dataengine-cli/blob/main/docs/references/commands/vastde_builders_list.md) to list available builder images.
  3. Run [vastde builders set](https://github.com/vast-data/dataengine-cli/blob/main/docs/references/commands/vastde_builders_set.md) to update the CLI configuration with the latest builder image URL:

```plaintext
user@user-machine:~$ vastde builders set v5.4.1-dev.c0b8b3d5
Using default repository, full image: vastdataorg/vast-builder:v5.4.1-dev.c0b8b3d5
Builder image URL updated successfully!

Previous: https://github.com/vast-data/dataengine-cli/releases/tag/v5.4.1-dev.c0b8b3d5
Current:  vastdataorg/vast-builder:v5.4.1-dev.29d4871e

This builder image will be used for building DataEngine functions
```
2. Rebuild each function and push it to the container registry. You can do this with [vastde functions build](https://github.com/vast-data/dataengine-cli/blob/main/docs/references/commands/vastde_functions_build.md):

```plaintext
user@user-machine:~$ vastde functions build my-function --target ./my-function-code --image-tag v2.0 --push
```
3. Update each function resource to point to its new image. You can do this from the DataEngine GUI:
  1. From the left navigation menu, select **Manage Elements** ( ![](https://cdn.us.document360.io/89b91113-5dc6-49db-86ec-57b16dc8ce56/Images/Documentation/how-to-upgrade-dataengine-runtime-en-image-sne1bxc2.png?sv=2026-02-06&spr=https&st=2026-11-08T09%3A29%3A48Z&se=2026-11-08T10%3A29%3A48Z&sr=c&sp=r&sig=abWCimnaloYmsIgU9ZrtnhzKM52XMSqg4b8SQSnA5rM%3D) ) and then **Functions**.
  2. Right-click the function and select **Edit**.

The revision number is incremented automatically from the previous revision.
  3. In the **Image Tag** field, enter the image tag attached to the new version of the container image.
  4. Modify other fields as needed:

| **Revision Alias** | An alias for the revision. |
| --- | --- |
| **Revision Description** | A description specifically for the revision. |
| **Container Registry** | The container registry where the image of the function is stored. If different from selected, select the correct container registry from the dropdown. |
| **Artifact Source** | The path on the container registry where the image resides. |
| **Full image path** | This is the full path to the image. It is formed automatically from the container registry, artifact source and image tag values that you supply. |
  5. Click **Update Function**.

A new revision is created and listed in the **Functions** page as a revision of the original function.
4. Redeploy each pipeline with new revisions of its functions:

When some of the pipelines have been redeployed with rebuilt function images, the Dashboard is updated to display new graphs (Active Pipelines, Failing Pipelines and Slowest Pipelines) under the heading System-Wide Overview: Functions And Pipelines Performance And Trends. At this point, the dashboard displays metrics of functions using the newer runtime version. However, metrics from any functions that are still using the old runtime version no longer appear.

Once all pipelines are redeployed, metrics from all functions appear. However, the error and the link to this upgrade guide continue to appear while traces from pre-upgrade invocations are still retained.
  1. From the left navigation menu, select **Manage Pipelines** ( ![](https://cdn.us.document360.io/89b91113-5dc6-49db-86ec-57b16dc8ce56/Images/Documentation/how-to-upgrade-dataengine-runtime-en-image-k5on3pft.png?sv=2026-02-06&spr=https&st=2026-11-08T09%3A29%3A48Z&se=2026-11-08T10%3A29%3A48Z&sr=c&sp=r&sig=abWCimnaloYmsIgU9ZrtnhzKM52XMSqg4b8SQSnA5rM%3D)) and then **Pipelines**.
  2. Right-click the pipeline and select **Go to Builder**.
  3. For each function:
    1. Select the function in the builder.
    2. Click **Settings** to show the function deployment configuration in the **Settings** pane on the right.
    3. From the **Revision Number** dropdown, select the new revision of the function.
  4. When you are done updating function revisions and making any other changes, click **Deploy**.

The pipeline is redeployed.
5. Once all pipelines are redeployed with rebuilt function images, at least one deployed pipeline has been triggered and the retention period for traces from older functions has transpired, you can navigate to the dashboard (click ![](https://cdn.us.document360.io/89b91113-5dc6-49db-86ec-57b16dc8ce56/Images/Documentation/how-to-upgrade-dataengine-runtime-en-image-dgz02jaq.png?sv=2026-02-06&spr=https&st=2026-11-08T09%3A29%3A48Z&se=2026-11-08T10%3A29%3A48Z&sr=c&sp=r&sig=abWCimnaloYmsIgU9ZrtnhzKM52XMSqg4b8SQSnA5rM%3D)) and see the new dashboard fully updated with new data.
6. Verify that under the heading **System-Wide Overview: Functions And Pipelines Performance And Trends**, you no longer see the error and you now see data. The graphs now include **Active Pipelines**, **Failing Pipelines** and **Slowest Pipelines**.