Mission scheduler is interval only: no day-of-week or time-of-day trigger

Aperta
  • Qualcosa non va?
#294 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
backend

Direzione di ricerca

The issue names no files or tests. Start by locating the mission definition and scheduler entry point, then trace how interval triggers are stored and calculated. Done means a mission can specify days of the week and a time of day, and the scheduler computes its next wall-clock fire rather than advancing an interval.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Reported in Discord #help by GaryP on 22 Aug 2026.

I have a task I run via macos launchagents every Mon, Wed, Fri at a selected time. the task trigger feature seems every X min/hours but not a every X at time Y. Do you think there is a way to get the Scheduler to do this (via some prompting I guess)?

Joyboy confirmed the limitation and described the fix in the same thread:

the mission scheduler is interval-only. There's no native day-of-week/at-time-Y. [...] Real fix would be a daysOfWeek + timeOfDay field on the mission and a scheduler that computes the next wall-clock fire

The workaround people are using today is to set a short interval and gate inside the prompt, for example "only proceed if today is Mon/Wed/Fri and the hour is H, otherwise stop". As Joyboy put it, that wakes roughly 24 times a day to act 3 times a week, and it is hour precise rather than minute precise.

GaryP settled on running his job every 24h at the time he first set it, accepting that it fires 7 times a week to do a job he wants 3 times a week.

Ask: daysOfWeek and timeOfDay on a mission, with the scheduler computing the next wall clock fire rather than counting an interval forward.

Filed from Discord triage.

Lingua principale
TypeScript
Stelle
8.5k
Fork
1.2k
Merge medio
13h 34m
PR unite (30g)
59

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di HarnessMD/munder-difflin

Tutte le issue di HarnessMD/munder-difflin

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.