[Bug]: cacheable: false does not take effect in YAML in v1.5.2, and cached replay clicks drift from the original positions

[Hellowlonewolf]

English Translation

In version 1.5.2, cacheable: false in YAML does not take effect. I also found that recorded scripts still use the cache during execution, which causes a low replay success rate. The click position used from the cache can differ from the click position in the first run.

Reproduction summary:

1. Use the Chrome extension to quickly record and generate a YAML script.
2. Add the cache configuration shown below and run it once.
3. On the second run, set cacheable: false for the step.

Expected: the step should not use the cache.
Actual: the report still shows that the cache is used, and replay reliability is poor because the cached click position can differ from the correct one.

---

Version

System:
    OS: Windows 10 10.0.19045
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i5-13500
    Memory: 8.32 GB / 31.69 GB
  Browsers:
    Chrome: 124.0.6367.91
    Edge: Chromium (133.0.3065.82)
    Internet Explorer: 11.0.19041.3636

Details

Reproduce link

null

Reproduce Steps

通过Chrome 插件快速录制生成yaml脚本文件
然后加入
agent:
enableTouchEventsInActionSpace: true
cache: # 缓存配置块
id: "son-yaml-v2"
声明缓存, 先运行一遍后, 在第二遍中 用例 cacheable : false
tasks:

• name: "Browsing different in-game 门客 characters"
  flow:
  • sleep: 1000
  • ai: "点击左下角门客字体按钮"
    cacheable: false
    最后在报告中他还是使用了缓存, 且使用缓存 脚本回放成功率低, 会有点击跟没有缓存的点击位置不一致