Cancel a stuck migration run¶

Only one migration can run at a time. If a run is still marked In Progress while nothing is running anymore, cancel it so a new migration can start.

When to use this

Starting a migration fails with A migration is already in progress.
A run on Media Migration Runs shows Possibly Stuck.

1. Prerequisites¶

You have the Media Storage Mgt. permission set.
You are sure the run is no longer running. Check Job Queue Entries for a job called FRW Picture Migration with status In Process.

Don't cancel a run that is still working

Cancelling only changes the status; it doesn't stop a session that is still running. A run that is still working continues in the background.

2. Steps¶

2.1. From Media Migration Runs¶

Open Media Migration Runs.
Select the run with status In Progress.
Choose Cancel Stuck Run and confirm with Yes.

The run gets status Failed.

2.2. From the setup page¶

When you choose Migrate Medias... on Media Bridge Setup while a run is still In Progress, Media Bridge offers to cancel it:

The run's session no longer exists (it was interrupted): the question defaults to Yes.
The run's session is still active: the question defaults to No, because it may still be working.

After cancelling, the wizard opens.

3. After cancelling¶

The cancelled run keeps its log. You can resume it later from Media Migration Runs: records that were already transferred are not uploaded again.

4. Verify¶

The run shows status Failed.
Migrate Medias... opens the wizard without a warning.

5. Things to know¶

A background run whose job crashes is marked Failed automatically. You don't need to cancel it.
Possibly Stuck is only a hint: a run is flagged after 24 hours in progress. It doesn't change anything by itself.

6. Common signals you may need this procedure¶

A migration is already in progress. If no migration is running, use the Cancel Stuck Run action on the Media Migration Runs page.

Follow step 2.1.