Old cycles still showing on the WUI

[esteban-abellan]

Description

I noticed that WUI is showing old cycles in one of the suites despite these cycles have been completed. I checked the cylc workflow-state and all tasks have been succeeded. I played with different Graph Window Depth but it doesn't have any impact on the old cycles. We are using the Cylc 8.3.5 version, and Cylc UI 2.5.0.

Note that this behaviour is not preventing the suite from cycling and it's only present in one of the suites. The rest of the suites, which use the same settings, are ok and do not display any previous cycle if N=0, only one if N=1 etc.

[oliver-sanders]

Hi @esteban-abellan 👋.

Can you confirm whether the extra cycles remain visible if you refresh the browser tab (this helps us work out what part of the system the problem originates in).

I can't replicate this with my own workflows, so I suspect that there is something about the workflow you are trying to run that is exposing this bug.

If you are able to share the [scheduling] section of the workflow, I can have a go at replicating the issue. Also, it would be handy to know if the workflow is defined in a suite.rc (back-compat mode) or flow.cylc (new style) file.

[MetRonnie]

Possible duplicate of #1813?

[ColemanTom]

This is a fresh load of the browser, so refreshing the tab does nothing to help. This workflow has not been showing the old cycles for a long time (although I notice it is the same one reported by @esteban-abellan). When we did a cylc stop; sleep; cylc play, they started building up again. But, other workflows which have near identical graph (changing some numbers in task names only), which stopped and started at the same time, do not have a buildup of old cycles.

Workflows are all defined in flow.cylc. There are no deprecation warnings. It may or may not matter, but, the workflows do use the cylc-rose plugin.

[ColemanTom]

Possible duplicate of #1813?

It might be, but in this case, I do not believe the n-window was adjusted since it started again. Maybe the n-window was different, then stop and play'd again, which changed the n-window, so that could be the same root cause. I would need to go through logs to check.

EDIT: I notice the n-window in this case is 0.

[MetRonnie]

This is a fresh load of the browser, so refreshing the tab does nothing to help.

In that case, this narrows it down to either a problem in the cylc-flow data store, or the UI's handling of "added" deltas in some circumstance.

@ColemanTom Does your workflow use suicide triggers? Or xtriggers?

[ColemanTom]

@ColemanTom Does your workflow use suicide triggers? Or xtriggers?

Yes to both.

Is there a command to extract the merged scheduling section from a workflow? If so I can do that and provide it.

Also, is there a graphql command I could run to pull out anything interesting?

[oliver-sanders]

Thanks for the info @ColemanTom.

Hopefully we'll be able to come up with a reproducible example for this one.

Also, is there a graphql command I could run to pull out anything interesting?

This query should list the tasks in each cycle point:

query {
  workflows(ids:["<id>"]) {
    familyProxies(ids: ["*/root"]) {
      cyclePoint
      childTasks {
        name
      }
    }
  }
}

It would be good to know what's going on with the empty cycles.

[ColemanTom]

query {
workflows(ids:[""]) {
familyProxies(ids: ["*/root"]) {
cyclePoint
childTasks {
name
}
}
}
}

Result was

{
  "data": {
    "workflows": [
      {
        "familyProxies": [
          {
            "cyclePoint": "20250130T1800Z",
            "childTasks": []
          }
        ]
      }
    ]
  }
}

WUI at the moment is displaying