Has anyone seen Flyte Propeller fail workflows with this failure?

Last known status message: AlreadyExists: Event Already Exists, caused by [event has already been sent]

I can''t tell if this indicates a larger issue or if Flyte Propeller should just be updated to more gracefully handle

AlreadyExists

. Going to dig deeper into this to understand if DB state was updated in Flyte Admin but maybe gRPC call failed the first time the event was sent..

hey @clean-glass-36808 is this still an issue in your environment? I've seen the

Already Exists

but there could be associated with transient communication issues between propeller and admin or propeller and the k8s informer. MapTasks are a common theme

Looking into it more it seems like the execution node was bouncing around states like moving to in progress and then being rerun in and old queued state so I think this is the cause for it trying to send duplicate events. I might have some more logs later but generally seemed like some sort of issue with the informer