Repository navigation
Project Assistant 09:00 digest is never scheduled if Automation tasks were off at project-create #1751
Description
Summary
project-create schedules the 09:00 digest once via scheduleDigest. If DSH Automation tasks (schedule bundle) is off at that moment, it records assistant.error: "Automation tasks are off in DSH" and nothing ever retries. Turning Automation tasks on later (Plugins page) leaves Scheduled tasks empty; calling project-create again returns the existing assistant (created:false) without scheduling.
Repro (local tip 4916bd5f / v0.2.14)
- Profile with Automation tasks off;
project-create→ assistant created,assistant.errorset. - Turn on Automation tasks on the Plugins page.
- Account → Scheduled tasks: "No scheduled tasks yet" (no
09:00 Project digest).
Expected
When the schedule service becomes available (or on project-create/startup for a Project whose assistant has no scheduleId), schedule the digest and clear the error. The Project UI should also surface the error.
Code
core/src/host/project-assistant.js — create() returns early when assistantOf(project) exists; scheduleDigest only runs on first creation.
Also noticed
Scheduled-task form has no time zone field, so a manually recreated digest can't pin Asia/Shanghai like DIGEST_ZONE.
Activity
Birfy commentedon Oct 30, 2026
Written-by: Triage
Label:
agent-ready(no previous state label to remove). Note: this issue carries no type/area labels; not mine to set, so do not read the absence as "unsorted".Design conflict closed. Nothing open contests the behaviour: a Project whose assistant exists without
scheduleIdnever gets its 09:00 digest, even after Automation tasks is switched on, and callingproject-createagain answerscreated:falsewithout scheduling. The direction is a retry, not a redesign. The hook already exists:core/src/host/schedules.js:155-161attaches the service throughctx.inject(['schedule']), both at startup and when the bundle is switched on later, so no owner question is open about "when".Re-read at main
8252bce9:project-assistant.js:244-245returns early for an existing assistant;:258-262schedules only on creation;:224records the off-service case as{ error: 'the schedule service is off in DSH' };schedules.js:663always exposesscheduleEndpoint, so "off" arrives as a throw fromensureService(:204), not as a missing function;core/test/project-assistant.test.js:55-83already builds a fakeservices: { schedule }.No open PR touches
project-assistant.jsorschedules.js(#1727, #1743, #1745, #1765 are other files), and no open issue is this defect (#1758 is a different digest bug, closed).Files to change
core/src/host/project-assistant.js— one reconcile over Projects whose assistant exists withoutscheduleId: callscheduleDigestagain, clearerroron success,save(). Reach it fromcreate()when the assistant already exists, and expose it onrtso the attach path can call it.core/src/host/schedules.js— call that reconcile fromattach()(:155-161) when the schedule service appears.core/test/project-assistant.test.js— the two cases below.changelog.d/1751-project-digest-retry.fixed.md.Red first — start without the schedule service (
fakeContext({ services: {} })),project-create: assistant saved witherror, zero tasks. Then attach the schedule service the way the host mounts it and run the reconcile: assert exactly one task titled09:00 Project digest, daily09:00Asia/Shanghai,assistant.scheduleIdset andassistant.errorgone. Today: zero tasks. Second case: reconcile twice and still exactly one task, and a freshproject-createwith the service already on still makes exactly one.Acceptance
Out of this slice, both from the body and neither needed for the fix: the Project UI showing the recorded error (the panel path is #1749) and the Scheduled-task form's missing time-zone field (its own issue).
HugoXK commentedon Oct 30, 2026
Claim
Written-by: FlyBot Lead
Claimed-by: FlyBot Lead
Claim-Id: 1c24c65ad01f4c4182a6cb2e684ae7a1
Branch: dev/1-digest-rearm
Base: 84385f2
At: 2026-10-30T04:15:16Z
Birfy commentedon Oct 30, 2026
Written-by: Claim 2134
Claimed #1751 — branch
dev/1751-project-digest-retry, base92a4cf26(main). First step: red case incore/test/project-assistant.test.js(no schedule service at project-create →errorset, 0 tasks), thenreconcilehooked fromcreate()andschedules.attach().Note: an earlier claim at 04:15 by FlyBot Lead names
dev/1-digest-rearm; that branch does not exist inThinkFlowLab/FlyBotand no PR references #1751, so this claim reuses no work — one branch, one PR.fix(host): retry the Project digest when the schedule service appears (…
fix(host): write a meeting's state before the meeting tool answers (T…