---
title: "\"Release with given UUID does not exist\" error when migrating flows"
slug: "release-with-given-uuid-does-not-exist-error-when-migrating-flows"
updated: 2026-05-06T19:46:33Z
published: 2026-05-06T19:46:33Z
canonical: "help.hyperscience.ai/release-with-given-uuid-does-not-exist-error-when-migrating-flows"
---

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

# "Release with given UUID does not exist" error when migrating flows

## Issue

When moving a flow from one instance of Hyperscience to another (e.g., from a development instance to production), a “Release with given UUID does not exist” error could appear in the Flow Studio for the imported flow.

![ReleaseWithGivenUUIDDoesNotExist.png](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/7335616700685.png)

## Affected versions

V31 and later

## Affected configurations

All configurations

## Cause

The imported flow is looking for a release with the UUID from the original instance.

## Solution / Workaround

1. Export the release from the original environment.
  - For more information, see “Exporting a Release” for your version of Hyperscience ( [v38](/general-information/docs/v38-exporting-a-release) | [v39](/v39/docs/exporting-a-release) | [v40](/v40/docs/exporting-a-release) | [v41](/v41/docs/exporting-a-release) | [v42](/v42/docs/exporting-a-release) | [v43](/v43/docs/exporting-a-release) ).
2. Import the release into the destination environment.
  - To learn more, see “Adding a New Release” for your version of Hyperscience ( [v38](/general-information/docs/v38-adding-a-new-release) | [v39](/v39/docs/adding-a-new-release) | [v40](/v40/docs/adding-a-new-release) | [v41](/v41/docs/adding-a-new-release) | [v42](/v42/docs/adding-a-new-release) | [v43](/v43/docs/adding-a-new-release) ).
3. (v32 and later) Assign the release to the flow in the destination environment.
  - For more details, see “Assigning a Release to a Flow” for your version of Hyperscience ( [v38](/general-information/docs/v38-assigning-a-release-to-a-flow) | [v39](/v39/docs/assigning-a-release-to-a-flow) | [v40](/v40/docs/assigning-a-release-to-a-flow) | [v41](/v41/docs/assigning-a-release-to-a-flow) | [v42](/v42/docs/assigning-a-release-to-a-flow) | [v43](/v43/docs/assigning-a-release-to-a-flow) ).