DC-to-cloud migration - Some apps are not registered to receive migration notifications

Cloud Migrations
, ,
1

Hi Community,
We are currently facing an issue with one of our DC-to-cloud migration customers.

image
image1420×346 116 KB

Their cloud app is not receiving notifications, even though we have followed the recommended steps as documented in the [official Atlassian cloud app registration guide](https://developer.atlassian.com/platform/app-migration/prepare-cloud-app-connect/).

Notably, all other customers have completed their migrations successfully using the same approach. This is the first time we have encountered this issue.

Here’s what we have already done:

  1. Webhook Registration:

We registered the webhook during the add-on install phase (lifecycle event).
The request sent is:

PUT /migration/webhook Body: {"endpoints": ["https://<our-url>/migration/notification"]} Endpoint: https://<customer-cloud-site>/rest/atlassian-connect/1/migration/webhook
  1. Descriptor Configuration:**
    We added the migrationWebhookPath in our atlassian-connect.json descriptor file:
"cloudAppMigration": { "migrationWebhookPath": "/migration/notification" }

Additional Information:
After installing our app, the customer changed their cloud site URL. We’re wondering if this change might be affecting webhook delivery or breaking the migration notification flow in any way.
Despite the above setup, the cloud app does not seem to be receiving any migration-related notifications.

Could you please advise:

  • Are we missing any critical configuration or steps?
  • What additional checks or troubleshooting steps can we perform to identify and resolve this issue?

Any help or suggestions would be greatly appreciated.

2

We encountered the same issue. Were you able to fix it? If yes could you tell me how?

3

Yes, we were able to resolve the issue.

In our case, the problem was that the following section was missing from the atlassian-connect.json descriptor file:

"cloudAppMigration": {
  "migrationWebhookPath": "/migration/notification"
}

After adding this configuration and redeploying the app, the migration notifications started working as expected.

Please ignore the part of my original post where I mentioned that this configuration was already present — that was incorrect.

Hope this helps!

2 Likes
4

Thank you for the information.

What is strange is that we already have this config, but client still got the notification about it missing. We tried to reproduce it but without success.

My theory is that because we had a major release (that required manual approval) it cause some bug with migration. The client sadly didn’t respond, so we can’t confirm it(but we asked him to check it, so maybe it really was it)

5

Hi @KamilParzyjaga,

If the Connect or Forge app has a major release, then the admin has to approve the update, and so without that they will still be on the previous atlassian-connect.json or manifest.yml descriptor.

It’s good to also use the other method and register the webhooks manually anyway in this case.

James.

1 Like