WarpCore

Symptom

In Older work, a project shows a sentence that starts “Stays on v” instead of Move to v5.
On a project's page, Move to v5 is grayed out, and a gray message that starts “Stays on v” says why.
After Move, a message starts “Stays on v” and nothing moved.

Likely causes

#	Cause
1	The newer version changes something that could spoil work already done, such as a removed task or a changed wait. The sentence names it, for example Stays on v4: v5 removes a task. Each reason is explained in Move work to a newer version.
2	The work itself cannot move now: it is still being set up, it is canceled, its property or engagement is deleted or an approval on it names an outside party.
3	Something changed between reading the list and pressing Move, for example the work was canceled. The message names the reason, for example Stays on v4: it is canceled.
4	The version chosen is not newer, or not published: “Work moves only to a published version.”
5	Your role does not allow moving work. Only a department manager or a company administrator sees Older work and the move.

No records

Checks

For causes 1 and 2, point at the grayed-out Move to v5 on the project's page, or read the project's row in Older work.
For cause 3, open Older work again: the list is read again after every refusal.
For cause 5, see Who can see and do what.

Fix

A refused change stays refused: the work finishes on the version it runs. To give it a fix, the template's owner makes a newer version whose difference the list allows, for example by rewording a task instead of removing it. Canceled work moves only after it is reactivated. Work that is still setting up can move once it is ready.

Confirm it worked

The project shows Move to v5 in Older work, and the move ends with a message that the work now runs the newer version.

Who to ask

Your department manager, or the person who looks after the template. See Move work to a newer version.

Work does not move to a newer version