[🐛 Bug]: Mismatch between WF card and Yaml contain

[diegovb-sys]

Describe the bug
The WF cards have a lable "Disable" to highlight this fact. Nevertheless, sometimes there is a mismatch between that label and the real contain in the Yaml.

This mismatch can lead to have the WF disabled while in the frontend it seems enable.

To Reproduce

At first sight, this problem seems to be random. Perhaps, the mix in modifications using the Builder or the Yaml could cause this.

Expected behavior
The expected behavior is to have a real sync between the label and the real status.

Screenshots
Button disabled:

[dosubot]

This mismatch can happen because toggling a workflow's enabled/disabled state via the API updates only the database field (is_disabled) but does not update the YAML (workflow_raw). There's a TODO in the backend code to update the YAML when toggling, but it's not implemented yet. As a result, if you switch between editing with the Builder and direct YAML edits, the UI and YAML can get out of sync, leading to the label showing the wrong status or the workflow being disabled in the backend while appearing enabled in the frontend. When updating a workflow via the YAML editor, the backend does sync the disabled field from the YAML to the database, but not the other way around. This is likely the root cause of the desynchronization you’re seeing. For reference, see the backend logic and comments here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}