let me try flipping on debug logs for dagit to see if I see anything

The last thing I’d check is to see if there are empty local files stored in your configured local path on your dagit pod.

There’s been lingering reports of issues where the S3 download fails but leaves an empty local file on the dagit pod, and then tricks dagit into thinking there are no logs, but haven’t gotten to the bottom of it. Can you also share what version of dagster you’re running?

websockets are on (well, they aren’t disabled in UI)

under the hood, the dagit pod is downloading the s3 content to the local FS and then reading them off disk

(also might double check your

dagster.yaml

and see if you’ve configured a different local path)

thank you btw :dagster:

I am unable to explain why this is working for me today lol