---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Verify the HashCode of a package version

# Verify the HashCode of a package version in RPA Hub {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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://www.servicenow.com/docs/~Gnhskj3_22Rndj8pp2Zag "As a system administrator, after you restructure the RPA Hub tables to extend the Application file (sys_metadata), you can use the update set capability to migrate your data from a lower (non-production) environment to a higher (production) environment for real-time use.").

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://www.servicenow.com/docs/jzWLGxZjdHbjKIPoHgk3nA "Upload a zip file of the automation package in RPA Hub to manually migrate the package from a lower (non-production) to a higher (production) environment.").

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://www.servicenow.com/docs/FX0I6PkBXL8cOAh00m_fwQ "Two-way integration of actions and subflows in Workflow Studio and RPA Hub for a seamless robot execution.").

## Procedure

1. Navigate to AllRobotic Process AutomationBuildPackages.
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://www.servicenow.com/docs/jzWLGxZjdHbjKIPoHgk3nA "Upload a zip file of the automation package in RPA Hub to manually migrate the package from a lower (non-production) to a higher (production) environment.").

*[\>]: and then