movePlan can only move plans that can be moved from Bamboo's move plan screen. For unknown reasons, some plans do not show up there . At least we have observed this for some plans on Bamboo 6.10.2 and have not previously seen this on earlier releases.
In any case, movePlans should throw an error in this case.
Under the covers, we may use movePlan to improve performance of the re-create plan because of Bamboo's delayed delete plan processing methodology that can introduce delays of a couple of minutes on re-create scenarios. Therefore, a createPlan may fail with this symptom
Plan XXX-YYYxxxxx not found.
Where the plan is a temporary plan name used in the move process.
Create plan will handle this case and just delete the original plan and then proceed to re-create
If createPlan uses addDefaultJob as one of the options, then we will avoid using movePlan and just delete the plan directly. Bamboo is better optimized to deal with the re-create scenario when using the default Bamboo behavior of automatically creating a default job and stage
Bamboo 6.10.2 at least.