Loading

CloudHub 2.0 deployment fails with "unknown error" after migrating from CloudHub 1.0 while the CloudHub 1.0 app is stopped/undeployed

Publiseringsdato: Jul 10, 2026
Beskrivelse
  • After migrating an app from CloudHub 1.0 (CH1) to CloudHub 2.0 (CH2), deployments/re-deployments of the CH2 app fail.
  • The UI shows a generic error such as: There was an unknown error while processing your request
  • MuleSoft backend logs for the migration/link step show an application-linking failure similar to:

[GET] CloudHubApplicationLinking returned HTTP response code 400 (CLIENT_ERROR) on endpoint http://console-admin.cloudhub.svc:8080/api/admin/applications/ch2/link?ch2_domain=<app-name>&ch1_domain=<app-name>&deployment_id=<deployment-id>&operation=link ... Message: Ch1AppName not found or Linked Previously.

  • The CH2.0 app remains in a NOT RUNNING/ Failed state after the migration completes.

 Cause: 

The CloudHub 1.0 → CloudHub 2.0 migration includes a linking step that connects the new CH2.0 application to its existing CH1.0 counterpart. This step requires the CloudHub 1.0 application to be running (deployed/started) at the time of migration.

If the CloudHub 1.0 app is stopped or undeployed when the migration runs, the platform cannot locate the running CH1.0 application to link it. The linking call fails (e.g., HTTP 400 with a message indicating the CH1 app was not found or was already linked previously), and the platform surfaces this to the user as a generic "unknown error." Because the link never completed successfully, later deployments of the CH2 app continue to fail.
Løsning
  1. In Runtime Manager, open the original CloudHub 1.0 application (the source of the migration).
  2. Start / re-deploy the CloudHub 1.0 application so it is in a running (deployed) state. Confirm its status shows as running before continuing.
  3. Re-run the CloudHub 1.0 → CloudHub 2.0 migration for the application while the CH1 app remains running. The linking step should now complete successfully.
  4. Verify the CloudHub 2.0 application deploys and reaches a running state without the "unknown error".
  5. Only after the migration, CH2.0 deployment and verifications are confirmed successful, stop or delete the CloudHub 1.0 application if it is no longer needed.
Knowledge-artikkelnummer

005388766

 
Laster
Salesforce Help | Article