From 70a63f8c6b0671ff7b3c3f34aeb652fbd0bc5597 Mon Sep 17 00:00:00 2001 From: Cal Corum Date: Mon, 2 Mar 2026 14:04:46 -0600 Subject: [PATCH] store: Issue Dispatcher: Separate systemd timer and service (not runner.sh template) --- ...stemd-timer-and-service-not-runn-1df35c.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 graph/configurations/issue-dispatcher-separate-systemd-timer-and-service-not-runn-1df35c.md diff --git a/graph/configurations/issue-dispatcher-separate-systemd-timer-and-service-not-runn-1df35c.md b/graph/configurations/issue-dispatcher-separate-systemd-timer-and-service-not-runn-1df35c.md new file mode 100644 index 00000000000..82549b613f9 --- /dev/null +++ b/graph/configurations/issue-dispatcher-separate-systemd-timer-and-service-not-runn-1df35c.md @@ -0,0 +1,28 @@ +--- +id: 1df35c2c-3749-4777-af9f-c6e2e5111979 +type: configuration +title: "Issue Dispatcher: Separate systemd timer and service (not runner.sh template)" +tags: [claude-scheduled, systemd, timer, issue-dispatcher, configuration] +importance: 0.6 +confidence: 0.8 +created: "2026-03-02T20:04:46.168718+00:00" +updated: "2026-03-02T20:04:46.168718+00:00" +--- + +# Issue Dispatcher Systemd Setup + +## Why Separate Units +The issue-dispatcher is its own script, not a task run by runner.sh, so it has dedicated systemd units rather than using the `claude-scheduled@.service` template. + +## Files +- `~/.config/systemd/user/claude-issue-dispatcher.service` + - `TimeoutStartSec=1800` (30 min for up to 3 issues) +- `~/.config/systemd/user/claude-issue-dispatcher.timer` + - Runs Mon-Fri at 09:45:00 + +## Key Config +```ini +[Service] +TimeoutStartSec=1800 +ExecStart=%h/.config/claude-scheduled/issue-dispatcher.sh +```