actually the run starts it s just the dagit UI that is not h

Question

actually the run starts it s just the dagit UI that is not happy about it trying to update the cluster to 0 13 16 to see if it works

daniel · Answer

very strange any idea what that upstream might be referring to is that in your code anywhere

Alessandro Marrella · Answer

nowhere in my code and the issue is not appearing when running dagit locally

Alessandro Marrella · Answer

so might be a dagster version mismatch issue some graphql query result that s different

Alessandro Marrella · Answer

Nope error still there after updating the cluster

Alessandro Marrella · Answer

ah you know what i think it s my envoy proxy returning upstream probably a timeout in handling the request