adrianakvo

Thanks Tim. I was planning to try this solution, but I don’t have the right access myself, so setting everything up to package the issue to a colleague to do the actual db change and this time it worked…

Not sure what I did, I think it must be something to do with the order of activation or page refreshing when other sites are being modified. But I went through these steps:

Uninstalled Jetpack on the entire site.
Waited over the weekend – think overnight could have been important.
Installed Jetpack on the Network.
Network Activated this over all sites.
Connected to WordPress.com (on the “dodgy” one first) – it worked.
Then connected on other sites in the set and each one worked fine.

Hope this helps anyone else with this issue – but apologies if not.

Cheers