I think I’ve sometime had this error spuriously too.

Leastways, I’ve run again from another session and it’s gone away