Hey all, we're running into an issue where our Fly...
# flyte-support
p
Hey all, we're running into an issue where our Flyte propeller logs are getting spammed with warnings that look like:
Copy code
{
  "json": {
    "exec_id": "aghjmv729fhfprjqchsk",
    "node": "[dynamicworkflowname]/dn50",
    "ns": "flyte-[project-name]-development",
    "res_ver": "385492809",
    "routine": "worker-0",
    "wf": "flyte-[project-name]:development:.flytegen.[dyanmicworkflowname]"
  },
  "level": "warning",
  "msg": "Subworkflow finalize invoked. Nothing to be done",
  "ts": "2025-05-10T08:17:41Z"
}
it's causing our propeller to keep crashing, and it's slowing down our Flyte system generally. This ties out with a dynamic workflow that is stuck in
ABORTING
state -- is there any way to get this unstuck / stop the flow of warnings into the logs?
a
The solve was to delete the
FlyteWorkflow
CRD
p
though just to note -- we had to manually patch out the finalizer before it would let us delete the CRD