Hi there! We attempted to deploy our first instance to Dagster Cloud via GitHub actions, and we ran into into a couple issues. 1. On our “welcome” page, the “Activating your deployment” section perpetually spins. This also appears in the “deployment” page (screenshots attached) 2. In our deployment logs, we receive the following error message:

Error: No Dagster Cloud agent is actively heartbeating. Make sure that you have a Dagster Cloud agent running.

We believe this is related to the first issue, but we aren’t sure on that. Has anyone experienced similar issues? And if so, is there a way to manually configure a serverless agent so we can deploy? Thank you in advance!

looking in to this now, believe it should be up and running soon

Sorry about that @Nathan Hawkins - you should be up and running again.

No worries, thank you both! I see now that the agent is active. For future reference, is this something that we could have fixed ourselves? Or was this something behind the scenes? Also, we’re receiving the following error message. It appears to be dealing with internals when initializing? Or is this something that we should handle on our end?

Exception: gRPC server exited with return code 1 while starting up with the command: "/tmp/pex-files/source-71481bc00f5168ca5ef71e27beb03e04c2b9b535.pex -m dagster api grpc --lazy-load-user-code --socket /tmp/tmpha_h529v --heartbeat --heartbeat-timeout 60 --log-level INFO --use-python-environment-entry-point --package-name dap_dagster"
  File "/dagster-cloud/dagster_cloud/pex/grpc/server/server.py", line 45, in CreatePexServer
    self._pex_manager.create_pex_server(
  File "/dagster-cloud/dagster_cloud/pex/grpc/server/manager.py", line 101, in create_pex_server
    server_process = GrpcServerProcess(
  File "/dagster/dagster/_grpc/server.py", line 1163, in __init__
    self.server_process = open_server_process(
  File "/dagster/dagster/_grpc/server.py", line 1064, in open_server_process
    wait_for_grpc_server(server_process, client, subprocess_args, timeout=startup_timeout)
  File "/dagster/dagster/_grpc/server.py", line 1004, in wait_for_grpc_server
    raise Exception(

Nothing on your end. It looks like your trial expired so we eventually spun the agent down. When you later went to add payment info, we just needed to manually spin the agent back up. I just took a look at your deployment - it looks like your code server can’t fully stand up because it’s missing an env var:

OSError: Failed because GCP_PROJECT is not set.

Gotcha. Thanks for the info! And yep, looks like we were using an outdated/mismatched version of dagster packages, which we resolved on our end. Running into different issues now, but those are on us 🙂 Thank you!