---
title: Troubleshooting SSP package import failure after copying a Record Event Trigger
slug: troubleshooting/troubleshooting-ssp-package-import-failure-after-copying-a-record-event-trigger
createdAt: 2026-11-18T14:34:30.928Z
---

Use this guide when a Swimlane solution package (.ssp) fails to import, and a playbook flow in the source tenant was created by copying and pasting a flow that contains a Record Event Trigger.

## Symptoms

**Import fails and shows:**

**Error Detected:** You must address this error to import successfully. `system-undefined-0-undefined: Unexpected error prevented importing the Swimlane solution package.`

The message does not name the playbook, application, or trigger. Import fails while the package is being opened, so the product cannot point to the item that needs to be fixed.

The same failure usually has these surrounding signs:

- The package was exported from one tenant and imported into another.
- The package includes playbooks.
- A package of newly built flows can import successfully, while a package that includes a copied flow fails.
- Opening the .ssp in a zip tool can prompt you to replace a file, because the same file name appears more than once under a folder named `OrchestrationTask`.

## Cause

Copying and pasting a flow that contains a Record Event Trigger can keep the original trigger's ID. Export then writes both triggers into the package under the same file name, for example, `OrchestrationTask/ab12c-34de5.json`.

The two copies are not the same trigger configuration, but they share that ID and file name. Import stops because the package contains that path twice.

A copied Playbook Button trigger can produce the same kind of duplicate file.

Turbine 26.1.4 assigns a new ID when a flow with a Record Event Trigger or a Playbook Button trigger is copied. That fix applies to copies made after the source tenant is on 26.1.4 or later. A flow copied before that upgrade can still contain the original ID. Recreate that trigger using the steps in the fix section, then export a new package.

Release notes:

- [Turbine Cloud 26.1.4](https://docs.swimlane.com/turbine-release-notes/turbine-cloud-2614-release)
- [Turbine On-Prem 26.1.4](https://docs.swimlane.com/turbine-release-notes/turbine-on-prem-2614-release)

## Diagnosis

Confirm the package itself before changing a playbook.

1. Match the import error to the message in Symptoms.
2. Use the exact .ssp that failed. It must be the file exported from the source tenant and imported into the destination tenant. If a newer export was created after other edits, check that file separately.
3. Open the .ssp with a zip tool. A solution package is a zip archive.
4. Open the `OrchestrationTask` folder.
5. Look for one file name that appears more than once. The zip tool may ask whether to replace `OrchestrationTask/<id>.json`.
6. Open the JSON files that share that name. Compare the playbook, the flow, and the trigger conditions. The shared ID is the file name. The rest of the configuration differs.
7. Find the flow that was created by copy and paste. Repair that flow. When an original flow and a copied flow both exist, leave the original trigger unchanged.

Swimlane Support can do this check from the .ssp if you would rather not open the archive.

## Where to make the change

Make the change in the source tenant, on the copied flow, before the next export.

- The destination tenant cannot repair a package that was already exported.
- The .ssp that failed will keep failing. Import only the new export.
- If several triggers in one package share a file name, repair each copied trigger, then export once.

## Fix for affected flows

Turbine 26.1.4 and later assign a new ID when a flow with a Record Event Trigger or a Playbook Button trigger is copied, so new copies export correctly. A flow copied before the upgrade still carries the shared ID. Recreate its trigger once, using the steps below, then export a new package.

1. Confirm the source tenant is on Turbine 26.1.4 or later.
2. Open the affected playbook and the flow that holds the duplicate trigger. If an original flow and a copied flow both exist, leave the original unchanged.
3. Open the Record Event Trigger. If the duplicate is a Playbook Button trigger, open that trigger instead.
4. Screenshot the full configuration: event type, conditions, filters, and mapped values.
5. Delete that trigger and save the playbook.
6. Create a new trigger of the same type and enter the settings from the screenshots. Building it by hand or copying and pasting the trigger or flow both work on 26.1.4 and later, because each new copy receives its own ID.
7. Review the copied actions. A paste can leave a reference to a field or action that was removed. Repair any missing reference before you export.
8. Save the playbook.
9. Export a new .ssp from the source tenant.
10. Import the new file into the destination tenant.

## Validation

1. Open the new .ssp with a zip tool.
2. Confirm that `OrchestrationTask` no longer contains the same file name twice, and that the zip tool does not ask you to replace a file.
3. Import the new package. Import should move past the error in Symptoms.
4. In the destination tenant, open the playbook and confirm the new trigger matches the screenshots.
5. When it is safe to do so, update a test record that meets the trigger conditions and confirm the flow starts.

## Contact Swimlane Support When

- The new package still fails after every repeated `OrchestrationTask` file has been removed and a new package has been exported.
- You cannot tell which flow was copied.
- The recreated trigger does not match the behavior of the trigger you removed.
- The source tenant was already on Turbine 26.1.4 or later when the flow was copied, and a copy made after that upgrade still exports a repeated trigger file.

Send the following with the request:

- The full import error text.
- The Turbine version of the source tenant. Include the version it was on when the flow was copied, if you know it.
- The source tenant name and the destination tenant name.
- The playbook name, the flow name, and the trigger type.
- Whether the flow was created by copy and paste.
- Screenshots of the trigger taken before it was deleted.
- The .ssp that failed, and the new .ssp if you have already exported again.

Support uses the package to confirm the repeated trigger file and the flow it belongs to. If a copy made after Turbine 26.1.4 still produces a repeated file, Support can send that for product review.
