Apologies… I’ve just seen that somebody else asked the same query and that this was fixed in v5.0.2.
This particular instance is still on v5.0.1, which explains why we’re seeing the problem. This is the perfect excuse for me to arrange for an upgrade to be done! 