Hi all - in our K8s deployment I'm often seeing a long list of "RUNNING" flows where the underlying pod has crashed (often due to OOM). Any ideas why these runs aren't reflecting a "CRASHED" state in the API?
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.