# Validation errors when moving a flow from one instance to another

- Published on Sep 24, 2024

- 1 minute(s) read

## Issue

When importing a flow or a release from one instance to another, validation errors appear in the flow, similar to the ones shown below:

```plaintext
Error: System secret referenced by input key "s3_config" does not exist. [reference_name: "submission_bootstrap"].
JSON path: `blocks.0.input.s3_config`
Error: System secret referenced by input key "ocs_config" does not exist. [reference_name: "submission_bootstrap"].
JSON path: `blocks.0.input.ocs_config`
Error: System secret referenced by input key "password" does not exist. [reference_name: "cob_export_uipath_d9393af1-0b8e-4186-904a-3493db739787"].
JSON path: `blocks.10.blocks.0.input.password`
```

## Affected versions

V30 and later

## Affected configurations

All configurations

## Cause

Instead of plain text versions of sensitive fields (e.g., passwords), we include references to these fields in an exported flow’s JSON file. Doing so ensures that those fields’ values cannot be seen in the JSON itself.

However, if you move the flow to another instance, these references become invalid, as the passwords are not saved in the destination instance.

## Solution / Workaround

To resolve the _s3\_config_ and _ocs\_config_ errors, you need to manually edit the flow’s JSON file to set the fields to their default values:

```plaintext
"s3_config": "${system.secrets.s3_downloader}",
"ocs_config": "${system.secrets.ocs_downloader}",
```

To resolve the _cob\_export\_uipath\_XXXX_ error:

1. Go to the imported flow’s settings in the application.
2. Open the UiPath Notifier Output Block’s settings.
3. Enter the password manually in the **Password** field.