i have configured a set of slaves to go offline as un-needed. a build job (buildJobA) has occurred on buildSlaveA and creates/leaves a successful workspace on the slave. A later in time build of buildJobA fires up buildSlaveB and successfully builds on buildSlaveB leaving a current and newer workspace on buildSlaveB.

Time and demand passes and buildSlaveB goes off line. Now select buildJobA on Jenkins and browse the workspace, you will be sent to the old build workspace on the "still up" buildSlaveA. This results in beatings for the build guy cause "you aren't pulling/building the latest stuff", even though the build guy shows the dev's that the good stuff IS on the buildSlaveB workspace via rdp/vnc.

suggestion:
either bring the sleeping slave on line to get to the latest workspace
OR
display some sort of warning about viewing and old workspace.