Agent 与自动化·github.com
Migrate hard-coded @Cron tenant jobs to workflow-backed schedules
目标用户 · developer
阅读原文 ↗Migrate hard-coded @Cron tenant jobs to workflow-backed schedules: ## Context PR #697 established the workflow-backed scheduling pattern: a predetermined per-org workflow, seeded OFF, toggled from the automation/workflow list, driven by the canonical `WorkflowSchedulerService` (per `ADR
个性化解读(发生了什么 / 为什么重要 / 影响 / 建议)将在接入 LLM 后按你的角色生成。
痛点信号
- migrate hard-coded @cron tenant jobs to workflow-backed schedules.
- it also fixed two latent scheduler bugs (status-casing filter + scheduled runs flipping to a terminal status) that any further migration depends on.
- this issue tracks converting the rest, one at a time, on the pattern pr #697 ships.
- - build any missing action nodes as reusable engine primitives (as `sendemail`/`trenddigest` were).
- - no tenant-product behavior left on a hard-coded `@cron`.
#developer#agent#issues