I think the problem was caused by the watch not being updated for some time; it now appears to have been updated correctly, so I'm going to mark this bug Invalid.
I think the problem was caused by the watch not being updated for some time; it now appears to have been updated correctly, so I'm going to mark this bug Invalid.