Has anyone had any issues with getting the timeline to dynamically refresh while a pipeline is executing. I can reload the page during execution and get the timeline to update but not in real-time. This is both when running Dagit within an Azure Web App or within k8s (behind Ambassador Edge). Chrome web console has a message like "failed: WebSocket is closed before the connection is established." Are there some timeout settings that may need to be adjusted when Dagit is behind a load balancer type setup?

the live execution view is powered by a GraphQL Subscription that happens over websockets. If something in the load balancer set up is causing the websocket connection to terminate, the live updates will stop

seems other websocket traffic is getting through fine except the live execution view. Are there any settings on server-side that can be changed?

no settings in

dagit

is it one persistent websocket connection or are new ones being set up repeatedly?

looks like many, did some more tests and looks like they are getting interrupted. Will do some more digging on potential settings in Ambassador

I'm actually experiencing similar issues. Just upgraded to 0.10.6 and the new deployment cannot connect to ws. The old could. Even if I portfowrad dagit from k8s.

I'm on 0.11.0 and k8s portforward of dagit isn't working either (in addition to ws via Ambassador)

cc @rex

live updating execution view

have you restarted the dagit pod? just want to rule out weird transient webserver state

confirmed same after restart of pod

i think the next step is probably to file an issue with as much detail as possible about your setup. I tried to repro on a few of our internal deploys and was unable to.

will include this in the issue but while the execution is running I can actually see payloads coming across in the websocket connection on chrome developer tab, seems its just not visualizing it until the page is reloaded

huh very weird

thanks for the details