maybe this is related to this error which came with the latest update:
Do you have the chance to test if it persists in an older version?