Migration job status codes

MySQL | PostgreSQL | PostgreSQL to AlloyDB

Overview

The following table lists, describes, and provides user actions for migration job statuses for Database Migration Service.

Migration job status	Description	Possible substatus	Possible user actions
Not started	The migration job is ready but still not running. This status is relevant if the migration job was created but wasn't started.	None.	Start. Delete.
Starting...	The migration job is in the process of being started. This is an intermediate status that occurs when a migration job is started. Starting the migration job takes between a few seconds and a few minutes. The status changes to `Running`.	None.	Delete.
Running	The migration job is actively running.	CDC, promote in progress.	Stop. Promote. Delete.
Completed	The migration job is completed. In the continuous migration type, this occurs after a successful promotion.	None.	Delete.
Failed	The migration job failed because of an error. Based on the type of error, the migration job may resume automatically, after the issue is fixed. Otherwise, the failure is unrecoverable, and the migration job needs to be restarted.	The last status before the migration job failed. Failed in CDC, Failed in full dump.	Restart. Delete. Promote.
Restarting	The migration job is in the process of being restarted.	None.	Delete.
Stopped	The migration job is stopped.	The last status before the migration job has stopped: Stopped in CDC.	If in the CDC phase, then the migration job can be resumed, promoted, or deleted.
Resuming	The migration job is in the process of being resumed.	None.	Delete.
Stopping...	The migration job is in the process of stopping after `Stop` was invoked. This is an intermediate status that occurs when a user stops a migration job. Stopping the job takes around a minute, during which the status is `Stopping`. Subsequently, the status changes to `Stopped`.	None.	Delete.