I've chased the team about this for you and if they haven't been already, they should be in touch soon.
I believe the team are still investigating this issue, however as soon as there is a resolution I'll post it here for you, @graeme.morrell1586282832334 and the whole of the community.
We still have the problem. And we have tried everything imaginable to fix it. Research shows that it has something to do with the API version used. We have tried all versions 11 to 13. Also a new APP on FB has led to the error.