I spent longer than I care to admit trying to figure out why my integrations weren't updating beyond their initial states, even while Connect servers in both kubernetes and docker compose were running, and not logging any overt errors.
It would help us literal-minded types if that status message indicated that the Connect server will not try to phone home until it's been tickled by a duly-authorized client. I understood my.1password.com to be telling me that the Connect server was not yet functional, so proceeding to the next step took a while to occur to me.
Thanks for your time.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided