Support #3643

Job plan fails when Rollback version package does not contain new target

Added by Vadim 22 days ago. Updated 20 days ago.

Status:FeedbackStart date:09/29/2020
Priority:NormalDue date:
Assignee:Vadim% Done:


Target version:RapidDeploy - 5.0-FIX
Affects Version:5.0-FIX Additional version details:
Timesheet Code:



I'm not sure if I didn't report it yet. But cannot find a ticket.

Problem is that when I edit project adding new target configuration I cannot deploy it as Rollback version does not contain that target. Seems that this is not a right one behavior as I physically cannot achieve that Rollback version until I make a successful deployment with a new configuration. I had to go to the job plan and set a Rollback plan item version to "Latest" to eliminate errors. But that's not good.

What do You think about this? Is that "as designed"? :)

Best regards,


#1 Updated by MidVision 22 days ago

  • Assignee set to Mariano
  • Target version set to 5.0-FIX

#2 Updated by Mariano 22 days ago

  • Assignee changed from Mariano to Vadim

Hi Vadim,

That's a good question. So, regarding rollback pipeline in job plan, the idea is revert changes. You can this automatically running same pipeline but using ROLLBACK version/package or set a custom rollback pipeline steps/jobs/versions.

When it comes to ROLLBACK version, this means that it uses the former succesfull version of the project and target combination. These means if you have run a Project A/Target A/Version 1 successfully, then you run same Project A/Target A/Version 2 sucessfully, if you rollback this, ROLLBACK version will use Version 1 to deploy. But in any case the project and target should be the same as before, Project A/Target A. I think it doesn't make sense to run a new target and then rollback this, because it doesn't exist in the previous version right?

Let me know if I wasn't clear or there is any doubt.


#3 Updated by MidVision 20 days ago

  • Status changed from New to Feedback

Also available in: Atom PDF