Find our responses and resources to address common app migration questions.
When the app migration starts the platform will match the listener to the app that is installed on the cloud site. The logic that is used to identify the listener is discussed here.
As an example, if you have Forge apps in commercial, in isolated cloud and/or AGC, you would define different listeners for each migration path (with their respective Forge app Ids defined under "getForgeAppId") and our platform will select the relevant listener to invoke.
As part of the progress reporting for Forge, we will transition a migration to FAILED or TIMED_OUT if we don't receive a status update for a message (i.e. AppData) within any 15 minute window after the data export has been completed.
When a migration is moved into a settled state (i.e. FAILED, SUCCESS or CANCELLED) requests will be rejected from the platform as the migration is now complete. The body of these requests will generally contain "Transfer 'XXX' is already in a settled state, no further actions are allowed".
Rate this page: