I believe I've had a similar issue a few times and might be due to some sort of asynchronous communication between the legacy and the new console.
It was solved by doing something like regenerating or importing the certificate in Smart Dashboard then exiting it, not publishing but editing the cluster object to view the certificate, press OK so the cluster object is also updated, then publishing and install the policy. I'm sorry I can't be more specific, I don't have right now an environment where I can check that but it was the idea.