Disabled server action steps can run

[Freemath22]

Wappler Version : 7.9.4
Operating System : Win 10
Server Model:
Database Type:
Hosting Type: local nodejs

Expected behavior

Disabled Server-side steps should not be executed

Actual behavior

It runs… (at least sometimes, at least step “include a library element”)

empty server action just to run in browser to see what happend in global

The result in browser, seems disabled server action step actually work

(Not only have I disabled the browser cache, but I also restarted both Wappler and the browser before launching it)

This is \app\modules\global.json

I'm trying to figure out how server actions and session variables actually work. Unfortunately, I’m seeing some glitches both when working in a single browser during reloads and across different browsers—I’m getting some illogical results. In this post, I’ll give an example of what adds to the chaos during debugging. You think a step is disabled, but it’s actually running.

How to reproduce:

Everything on the screenshots.

[Freemath22]

If I add a variable to Global and then disable it, the global.json file will look like this:
[
"lib/lib_ses",
{
"name": "test_var",
"module": "core",
"action": "setvalue",
"options": {
"value": 1
},
"meta": ,
"outputType": "text",
"output": true,
"disabled": true
}
]

An “disabled” field appears for the variable. There is no such field for the “include” step. Nor is there such a field in the lib_ses.json file.
However, after restarting Wappler, the interface still shows that the “include” step is disabled. Where does Wappler get this information?