When a local refinement (new) job is cloned (in v3.1), if the rotation and translation search extents are previously set to 20 degrees and 10 A with the gaussian prior on, they always reset themselves to 9 degrees and 3 A after cloning the job.
This is not really a big problem, but it does make it easy to mistakenly run a job with unintended parameters. Strangely, if they are set to anything else - e.g. 25 and 15 - they do not reset themselves. I guess this may have something to do with the fact that 20 & 10 are the defaults with the gaussian prior on.