There was a bug reported for that recently that has since been fixed:
Could you try updating your site and see if that resolves things?