Are you waiting for a MigrationWiz job to come back when it has actually stopped processing and will not recover without intervention?

In a throttled MigrationWiz job, throughput drops and items per hour can fall sharply, but the migrated item count keeps moving. A hung job looks different: for 30 minutes or more there is zero item progress, no useful error in the activity log, and the migrated count does not change even though the job still reports as running.

EWS throttling is designed to clear without manual action. MigrationWiz reads the retry-after value returned in the throttling response, waits through the required back-off period, and then resubmits automatically. Restarting is not needed, and manually stopping and restarting can reset queue position and delay recovery.

A hung job, by contrast, typically does not self-recover. This pattern most commonly occurs when the OAuth access token for the source or destination endpoint expires mid-job. MigrationWiz does not always surface token expiration as a hard error. It may simply stop writing items while continuing to report the job as running.

To recover, stop the job, reauthenticate the endpoint it is tied to, and restart. MigrationWiz will resume from the last successfully migrated item timestamp.

Can you distinguish between a throttled MigrationWiz job and a hung one from your current dashboard monitoring?

#BitTitan #MigrationWiz