zai-org / zai-org/feedback

[Bug] Schedule tasks not running

Open
#219 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2 status: 待评估 type: Bug
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

提交前确认 · Pre-submission checklist
  • 我已搜索过现有 issue,确认这不是重复 / I searched existing issues and confirmed this isn't a duplicate.
  • 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category

UI / 界面体验 · UI / UX

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

严重程度 · Severity

阻塞使用 · Blocking (无法使用核心功能 / core function unusable)

复现频率 · Reproducibility

必现 · Always

问题描述 · Description

Schedule tasks not executing.
Tried a default one
tried a custom one
Result:
Could not trigger run

复现步骤 · Steps to reproduce

trigger manually or by time results in Could not trigger run

期望表现 · Expected behavior

trigger scheduled task

实际表现 · Actual behavior

popup
Could not trigger run

ZCode 版本 · ZCode version

3.6.5

设备 / 系统 / 浏览器 · Device / OS / Browser

Windows 11 - wsl

截图 / 录屏 / 日志 · Screenshots / Recordings / Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files, tests, or entry points are identified in the report. Start by reproducing the failure on Windows 11 with WSL using both a default and a custom schedule, manually and by time; done means the scheduled task triggers without the “Could not trigger run” popup.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.