Also seeing this in the UI when I go to Launchpad, which definitely looks like a dagster-cloud issue and not a user issue:

dagster._core.errors.DagsterUserCodeUnreachableError: dagster._core.errors.DagsterUserCodeUnreachableError: Could not reach user code server. gRPC Error code: UNAVAILABLE

Stack Trace:
  File "/dagster-cloud/dagster_cloud/agent/dagster_cloud_agent.py", line 834, in _process_api_request
    api_result = self._handle_api_request(
  File "/dagster-cloud/dagster_cloud/agent/dagster_cloud_agent.py", line 625, in _handle_api_request
    serialized_subset_result_or_error = client.external_pipeline_subset(
  File "/dagster/dagster/_grpc/client.py", line 292, in external_pipeline_subset
    res = self._query(
  File "/dagster/dagster/_grpc/client.py", line 156, in _query
    self._raise_grpc_exception(
  File "/dagster/dagster/_grpc/client.py", line 139, in _raise_grpc_exception
    raise DagsterUserCodeUnreachableError(

The above exception was caused by the following exception:
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNAVAILABLE
	details = "failed to connect to all addresses"
	debug_error_string = "{"created":"@1673649755.093790712","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3260,"referenced_errors":[{"created":"@1673649755.093789916","description":"failed to connect to all addresses","file":"src/core/lib/transport/error_utils.cc","file_line":167,"grpc_status":14}]}"
>

Stack Trace:
  File "/dagster/dagster/_grpc/client.py", line 154, in _query
    return self._get_response(method, request=request_type(**kwargs), timeout=timeout)
  File "/dagster/dagster/_grpc/client.py", line 129, in _get_response
    return getattr(stub, method)(request, metadata=self._metadata, timeout=timeout)
  File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 946, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)

hey sterling - is this in a branch deployment or a full deployment?

Full deployment

Hi sterling - are you still seeing this? Things look healthy to me at the moment and I see runs kicking off.

The scheduled version of the job ran at 3:00p Pacific and it ran fine. It’s only an issue through Launchpad

This error means that the agent can’t read your code - usually it happens on startup of a new location but it could be an intermittent failure of the code server. what are the steps to reproduce the issue?

It was happening when I would go to launchpad and wait a moment.