I’m trying to get to the bottom of why we appear to receive duplicate listener-triggeredmigration eventType messages.
The messages have same same values for migrationId, transferId, migrationScopeId, createdAt, cloudAppKey, cloudUrl, jiraClientKey and confluenceClientKey but different messageIds.
The docs hint that we could get two listener-triggered events because it says: “Notifies your cloud app when core product data migration is complete or incomplete” but I don’t know how to differentiate between a complete vs incomplete event.
The docs hint that we could get two listener-triggered events because it says: “Notifies your cloud app when core product data migration is complete or incomplete” but I don’t know how to differentiate between a complete vs incomplete event.
I believe that this not the actual intention behind ‘complete vs incomplete’. What is being stated here is that core migration can either finish in two potentially states from which app migrations can begin; COMPLETE or INCOMPLETE. This refers to the status that you can see in the CMA.
The core migration can be one status or the other - not both. You should receive a listener-triggered event if it is one of these two statuses.
For completeness sake, you should not receive a listener-triggered event if the core migration has failed.
I don’t believe our docs indicate that you should only ever receive a single listener-triggered event per transfer - but I completely understand why it’d be confusing to receive multiple with different messageIds.
I’ve raised this query internally and hopefully we’ll be able to come back to you sooner rather than later
