v3.5.11 : Workflow stuck in running state even after successful completion of workflow

[shivani-cell]

Pre-requisites

• I have double-checked my configuration
• I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
• I have searched existing issues and could not find a match for this bug
• I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

It should mark workflow as succeeded state, but it is in running condition from past 6 days.

Version(s)

v3.5.11

Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

We cannot produce the similar issue.

Logs from the workflow controller

kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

we redeployed workflow controller by attaching  workflowtaskresult to service account role.But it also didn't work successfully and able to mark workflow as completed

Logs from in your workflow's wait container

kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

It is showing no resources found in <namespace> namespace
 but using kubectl get wf <workflowname> -n <Namespace>
It is showing running state

[blkperl]

hey @shivani-cell did you check to see if your issue is related to #13937?

Unfortunately, without a workflow that reproduces the issue no one can investigate or debug this. Please update the description with a workflow that reproduces the issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity and needs more information. It will be closed if no further activity occurs.

[tooptoop4]

where @shivani-cell