---
title: Verify the HashCode of a package version in RPA Hub
description: Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/view-hash-code.html
release: australia
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 2
breadcrumb: [Package and package version, Use, RPA Hub, Robotic Process Automation \(RPA\) Hub, Workflow Data Fabric]
---

# Verify the HashCode of a package version in RPA Hub

Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record.

## Before you begin

You must do this task in the classic environment.

Ensure that you’ve completed the tasks that are related to migrating your data from a lower environment to a higher environment. For more information, see [Migrating your data from a lower environment to a higher environment in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/migrate-data-rpa-hub.md).

Ensure that the **sn\_rpa\_fdn.allow\_manual\_upload\_of\_automation\_package** system property is marked as true. If you have the admin role, you can edit this system property.

Upload an automation package. For more information, see [Upload an automation package attachment in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/upload-package-version-attach.md).

Verify that the life-cycle stage of the package version isn’t set to **Retired**.

Role required: sn\_rpa\_fdn.rpa\_release\_manager or sn\_rpa\_fdn.rpa\_admin

## About this task

A HashCode is a unique, auto-generated alphanumeric value of a published package version that is used to validate the integrity of the package version. The system verifies the HashCode of the first attachment that is uploaded on the package version record. To ensure a successful validation, upload only the correct attachment.

Another way to verify the HashCode of a package version is via triggering the **Verify HashCode of a Package Version** Action in Workflow Studio. For more information, see [Workflow Studio actions and subflow in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/rpa-hub-actions.md).

## Procedure

1.  Navigate to **All** > **Robotic Process Automation** > **Build** > **Packages**.

2.  Open a package to view the HashCode.

3.  On the **Package Versions** tab, select a version.

4.  In the form header, select **Verify Hash Code**.


## What to do next

If the HashCode validation fails, remove the invalid attachment and upload the correct automation package. For more information, see [Upload an automation package attachment in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/upload-package-version-attach.md).

**Parent Topic:**[Package and package version in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/package-version-rpa-hub.md)