Can't say I've ever seen that expected state line, but it wouldn't surprise me either. Can you confirm that this is happening in Automate 2, not Automate 1.x?
If yes, the root cause of the issue here might be that you need to configure Automate with whatever DNS name you're going to use to access the site.