This has been raised a couple of times now and we have acknowledged it.
This team is working to resolve this issue.