Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Run a scheduled job now, to see it work without waiting for its clock

Open
  • Is something wrong?
#467 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@19BEC0802 is already working on this.

Since Oct 15, 2026.

  • #468 by @19BEC0802 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
backend, frontend

Research direction

Work is already under way: pull request #468 is open against this issue. The change spans the open schedule row UI and the main-process timers. Start by finding where sendMission and lastFiredAt are set for scheduled jobs, and where main re-arms the timers. Done means a Run now button sends the saved job immediately with the same run message, refuses a second run within a minute, and leaves set-time slots unchanged.

Written by the indexing model from the issue text.

Description

enhancement
Problem / motivation

An owner who sets up a job on a clock cannot see it work until the clock comes round. "Check the support inbox" every hour means waiting up to an hour for the first run; a Monday 9:00 summary means waiting up to a week. If the job's name or focus area needs a change, the owner edits it and waits again. The only way to try a job today is to retime it to a minute from now and set it back, which also moves its real slots.

Proposed solution

A "Run now" button in the open schedule row, beside Close and Save. It sends the job at once exactly as its clock would (the same sendMission, the same run message, lastFiredAt stamped the same way), so a run now is a faithful test.

  • Jobs only: never the heartbeat or a compact row.
  • Never sent twice: main refuses a run within a minute of the job's last run.
  • An every job counts from the run (main re-arms the timers, so the row and the timer agree); a job at set times keeps its slots.
  • Only the saved job runs: Run now is off while the row has unsaved edits.

I have this built and tested and would like to open the PR.

Screenshot, mockup or recording
Image
Alternatives considered

Retiming the job to a minute from now and setting it back: it works, but it moves the job's real slots and needs two edits each time. Lowering the interval to test has the same problem.

Area

Office floor / avatars

Pre-flight
  • I attached a screenshot, mockup or recording above.
  • I searched existing issues and discussions, and this isn't a duplicate.
Dominant language
TypeScript
Stars
273
Forks
211
Avg merge
13h
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from agentvivekkumar/dontbemichael

All issues in agentvivekkumar/dontbemichael

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.