Completed workflows appear as running in workflow list ui

Community Support
1

Hi,
we have a weird issue with completed workflows still showing in the UI as running.

Capture d’écran du 2025-02-05 16-24-08
Capture d’écran du 2025-02-05 16-24-081923×182 46.4 KB

When I describe or query the workflow, everything seems ok :

temporal workflow describe --workflow-id analyze-ftp-SINA01398-demo-891dc036-9100-4023-bf57-e4b17921e9d7 --run-id 1404beab-1e4a-4a95-b249-288242e8c6ee

{
  "executionConfig": {
    "taskQueue": {
      "name": "worker-queue",
      "kind": "Normal"
    },
    "workflowExecutionTimeout": "0s",
    "workflowRunTimeout": "0s",
    "defaultWorkflowTaskTimeout": "10s"
  },
  "workflowExecutionInfo": {
    "execution": {
      "workflowId": "analyze-ftp-SINA01398-demo-891dc036-9100-4023-bf57-e4b17921e9d7",
      "runId": "1404beab-1e4a-4a95-b249-288242e8c6ee"
    },
    "type": {
      "name": "AnalyzeRemoteServerWorkflow"
    },
    "startTime": "2025-02-05T13:56:06.403057592Z",
    "closeTime": "2025-02-05T13:56:06.614598694Z",
    "status": "Completed",
    "historyLength": "18",
    "executionTime": "2025-02-05T13:56:06.403057592Z",
    "memo": {

    },
    "searchAttributes": {
      "indexedFields": {
        "BuildIds": "[\"unversioned\"]"
      }
    },
    "autoResetPoints": {

    },
    "stateTransitionCount": "11",
    "historySizeBytes": "2835",
    "mostRecentWorkerVersionStamp": {

    }
  }
}

temporal workflow query --workflow-id analyze-ftp-SINA01398-demo-891dc036-9100-4023-bf57-e4b17921e9d7 --run-id 1404beab-1e4a-4a95-b249-288242e8c6ee --type “__stack_trace”

Query result:
["Workflow is closed."]

We have to manually delete workflow to “clean” the UI with temporal workflow delete ...

Anything we could do wrong here?
Thanks.

1 Like
2

Capture d’écran du 2025-02-05 16-24-31
Capture d’écran du 2025-02-05 16-24-311952×878 87.4 KB

Including the other screenshot here.

1 Like
3

I’m also facing this issue, not sure what to do about it other than just cleaning up.

4

If you are running visibility on SQL db:

Upgrade to 1.27.1+ server version and see if you run into this again
see release notes here
specifically “Fix out-of-order Visibility tasks with SQL database” section