I haven't seen the same error since, so hopefully it's a one-off. But I'll get hold of you if it comes back up again.
