<#6520 [BUG] Flyte Propeller Redundant Workflow De...
# flyte-github
c
#6520 [BUG] Flyte Propeller Redundant Workflow Detection isBroken Issue created by Sovietaced ### Flyte & Flytekit version Flyte v1.15.X ### Describe the bug Flyte Propeller has logic to avoid writes to etcD when the in-memory workflow status is unchanged. Unfortunately it does not work because the task node status always seem to be dirty even when there is no diff. This is because the task node status id unconditionally set to dirty when
setX
calls are made to it. There may also be a problem with comparing unserialized values that will never be present from workflows read from etcD. ### Expected behavior I would expect Flyte Propeller to avoid writes to etcD when there is no diff in the workflow status. ### Additional context to reproduce No response ### Screenshots No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte