It seems like the issue you're facing with the HTTPSConnectionPool in the SDK WorkspaceClient when using it within a workflow may be related to the environment variables or credentials not being propagated correctly. When running the notebook manually, it recognizes the host and port, but within the workflow, there's an error with the connection pool. Check if the necessary environment variables and credentials are set properly within the workflow environment. Additionally, ensure that the notebook task in the workflow inherits the correct context or configurations from the preceding task. It might be helpful to explicitly set the host and port in your notebook code or review any specific requirements for SDK usage in the workflow. If the default Databricks notebook authentication is not working as expected, you might need to explore alternative authentication methods or contact Databricks support for further assistance.

Maybe this will be useful for you too!