Adobe Sandbox Tooling failure when copying AJO Campaign Orchestration audiences between sandboxes

We recently discovered an issue in AJO. Logging details here for the community visibility so others can easily debug such problem

Bug Title Sandbox Tooling failure when copying AJO Campaign Orchestration audiences between sandboxes.

Product Product: Adobe Journey Optimizer (AJO) Campaign Orchestration Component: Sandbox Tooling.

Expected Behavior Sandbox tooling should successfully migrate an audience package from a dev sandbox to a stage environment. If components such as merge policies are already present, the system should gracefully handle the conflict by prompting to overwrite or ignore the component rather than failing the import.

Observed Behavior Attempting to import a package containing an AJO Campaign Orchestration audience fails during the upload. The import returns an OBJECT_EXISTS error ("PROFILE_MERGE was not created anew") for merge policies that already exist in the target sandbox. Additionally, it returns a NEBULA-100092-400 error claiming an invalid or missing namespace, despite the 'person id' namespace being verified as active in both sandboxes.

Steps to Reproduce

1. Access AJO Sandbox Tooling in the source (dev) sandbox.
2. Create a package containing an AJO Campaign Orchestration audience .
3. Ensure the destination sandbox already contains the associated merge policy and ‘person id’ namespace.
4. Attempt to import the package into the destination sandbox.
5. Observe the package import failure and review the resulting OBJECT_EXISTS and NEBULA-100092-400 error logs.

Root Cause Assessment The platform currently processes an AJO Campaign Orchestration audience copy similarly to an external RTCDP audience, which unsupported because it effectively requires copying an entire database table rather than just the audience definition. Furthermore, the import logic lacks conflict resolution for pre-existing components like merge policies.

Business Impact Operational disruption. The inability to utilize automated sandbox tooling for Campaign Orchestration audiences forces teams to abandon package deployments and manually recreate audiences in destination sandboxes. This increases deployment overhead, delays testing cycles, and introduces the risk of human error during environment promotion.

Workarounds Applied Manually recreating the audience in the destination sandbox using identical segment logic and ensuring all related segment namespaces and integrations are manually aligned.

Requested Next Steps from Adobe

1. Fast-track and deploy the pending major release for AJO Campaign Orchestration sandbox copy support.
2. Update the Sandbox Tooling import logic to handle existing components via overwrite or ignore prompts instead of generating hard failures.