Just mentioning we are experiencing the same issue. At this stage we don't have a solution but will be trying to redeploy and will update once it's done.