Change "Could not continue build execution. The result has no continuable jobs." message

Problem Definition

The "Could not continue build execution. The result has no continuable jobs." message addresses the fact that a manual stage cannot be triggered and continue running if the job that it was originally supposed to trigger no longer exists. Suppose you run a build right now with stages A and B (manual) but never trigger the second manual stage B (so the build is incomplete). A few days later you decide to remove the job inside the manual stage and replace it with another job. If you try to start the manual stage B now it will throw this message because the job it was originally supposed to run doesn't exist anymore so it can't continue.

The problem I want to address in this feature request happens when we trigger the same message for a different use case. If the change you make after you triggered the build and before running the manual stage is related to the repositories in your plan the manual stage won't get triggered but not because the job in that stage doesn't exist anymore – because the repositories were updated. When repositories are updated Bamboo doesn't know whether revisions from the repositories that were added or removed are relevant for the plan execution anymore and doesn't allow users to continue the build.

Suggested Solution

Add a more informative/ descriptive message to let users know why they can't continue building and run the manual stage when there's a repository update/ change in the plan rather than the "Could not continue build execution. The result has no continuable jobs." message which is a bit misleading since jobs are not playing a role here.