Hi everyone, When an Airbyte sync fails prematurely (e.g., due to an image pull failure from the registry) with 0 records synced, Airbyte is still reporting the status as Successful. This false-positive status makes it easy to miss silent failures. I noticed an open issue tracking this on GitHub (Replication pod creation fails (KubeClientException) but UI/Public API still reports sync as successful · Issue #72448 · airbytehq/airbyte), but in the meantime, I wanted to check: how are others currently detecting and handling these false-positive syncs? Any workarounds or monitoring approaches you’d recommend?