Closed
Labels
area:automationScheduled tasks and automationScheduled tasks and automationenhancementNew feature or requestNew feature or request
Description
Follow-up to #354 (its first slice, Edit + Pause/Resume + documented missed runs, is in the PR that Fixes #354). This issue holds the rest of #354's scope, which the Owner decision of 2026-10-20 left for later.
Expected behavior
- Last run and failures. Each scheduled task in Settings → Scheduled tasks shows when it last ran and whether that run failed, with a reason. DSH's catalog already carries
lastDelivery(inbox delivery receipt, not the model's result), andhistorygives saved deliveries; a run's actual outcome (the Bot's turn finished or failed) is FlyBot's to record. - Retry. A failed run can be run again from its row with one click.
- "Needs you". A failed run shows up where the owner looks for attention, through Proactive reminders 1/3: event reminders (approval waiting, failed, finished) in app and desktop #353's notifications and [Feature RFC] Agent inbox board: one place for tasks, approvals and failures (personal first, team second) #349's Agent inbox (the triage of Proactive reminders 2/3: scheduled tasks and recurring summaries #354 placed it there).
- Limits (aligned with [Team] Bound agent loops and resource consumption #56): caps on tasks per person, the smallest repeat interval, run time and cost.
Scope / open questions for the owner
- What counts as a failed run: DSH could not deliver the reminder, the Bot's turn errored, or the turn ended without an answer?
- Retry: run the same prompt now (an extra run) or re-deliver the missed one?
- The limit values ([Team] Bound agent loops and resource consumption #56) and whether they apply per Bot or per person.
Depends on #353 and #349 landing first. Needs the owner's decisions above before agent-ready.
Metadata
Metadata
Assignees
Labels
area:automationScheduled tasks and automationScheduled tasks and automationenhancementNew feature or requestNew feature or request
Activity
Birfy commentedon Oct 20, 2026
Maintenance triage (2026-10-20 09:56 Asia/Shanghai, main
465357e): still needs-human; depends on #353/#349 (PRs #470/#472). Proposed answers for the owner to confirm:agent-readyonly after the owner's answer.Birfy commentedon Oct 20, 2026
Owner decision (2026-10-20): option (a) as recommended — a run fails only when DSH delivery fails or the Bot turn errors (a finished turn with no answer is not a failure). Each task row shows last run time, result and reason; Retry re-runs now with the same prompt (no backfill of missed runs); failures also surface in notifications and the Agent inbox. Limits (#56) not in this step.
Edit and pause scheduled tasks; document missed runs (ThinkFlowLab#474)
Birfy commentedon Oct 20, 2026
Claimed by maintenance run (2026-10-20 11:55 Asia/Shanghai, main
a7adfe0): developing on branchfeat/473-schedule-last-run-retryin Birfy/FlyBot, following the Owner decision above (first slice only).Birfy commentedon Oct 20, 2026
Minor decisions for #473 (decided by the maintenance worker under the owner's delegation, 2026-10-20 12:08 Asia/Shanghai), PR #494:
Merge origin/main into feat/473-schedule-last-run-retry
Show each scheduled task's last run, and Retry a failed one (ThinkFlo…