Hi Jo - Our apologies! We've now fixed the issue with the new tab you're describing here. Only users with certain settings encountered the issue, so we missed it in testing. Thanks for letting us know!