cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
main
claude-memory/graph/configurations/issue-dispatcher-separate-systemd-timer-and-service-not-runn-1df35c.md
Cal Corum 96874fc2be relate: 2d98e145 --RELATED_TO--> 1df35c2c
2026-03-02 14:05:39 -06:00

1.7 KiB
Raw Permalink Blame History

id type title tags importance confidence created updated relations
1df35c2c-3749-4777-af9f-c6e2e5111979 configuration Issue Dispatcher: Separate systemd timer and service (not runner.sh template)
claude-scheduled
systemd
timer
issue-dispatcher
configuration
0.6 0.8 2026-03-02T20:04:46.168718+00:00 2026-03-02T20:05:39.459540+00:00
target type direction strength edge_id
cb5e8814-f689-4de0-8854-823358706dec RELATED_TO outgoing 0.78 a476cd48-527f-4326-8e20-2bce41ada2fd
target type direction strength edge_id
b27fb831-811e-4103-b5f1-3c36d5b1ad20 RELATED_TO outgoing 0.78 c2569dab-7309-403b-abfc-15da002c33cd
target type direction strength edge_id
62ee21e8-2b56-4d38-a73d-47e2724f08c6 RELATED_TO outgoing 0.76 a649f391-20c5-43a1-a4c3-5b300f02d43f
target type direction strength edge_id
c4b2f42d-b443-447f-8a05-bba099e06036 REQUIRES incoming 0.8 8719b756-9563-4c2d-85ef-4a5700354489
target type direction strength edge_id
2d98e145-1de7-4ea2-8bfb-fd89c364fbcc RELATED_TO incoming 0.8 0ffaf711-6a34-4aa5-8c28-1a0e9129c52e

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

[Service]
TimeoutStartSec=1800
ExecStart=%h/.config/claude-scheduled/issue-dispatcher.sh