# Scheduler - run now

**URL:** <https://community.zammad.org/t/scheduler-run-now/14417>\
**Category:** Feature requests\
**Tags:** zammad-73\
**Created:** [May 24, 2024, 10:39am UTC](https://community.zammad.org/t/scheduler-run-now/14417 "2024-05-24T10:39:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrklo](https://community.zammad.org/user_avatar/community.zammad.org/chrklo/32/464_2.png) [@chrklo](https://community.zammad.org/u/chrklo)\
**Post date:** [May 24, 2024, 10:39am UTC](https://community.zammad.org/t/scheduler-run-now/14417/1 "2024-05-24T10:39:36Z")

</div>

Title: scheduler - run now

1. What is your original issue/pain point you want to solve?  
I would like to execute a Scheduler entry immediately.  
Current workaorund: I set the next possible time and then wait for the execution.  
Then I remove the time again.
2. Which are one or two concrete situations where this problem hurts the most?  
We delete spam tickets regularly.  
However, tickets have also been marked as spam by mistake.  
That’s why I check before deleting.
3. Why is it not solvable with the Zammad standard?  
Currently not implemented
4. What is your expectation/what do you want to achieve?  
Quick execution of a scheduler entry

---

<div class="post-metadata">

**Author:** ![foss4ever](https://community.zammad.org/user_avatar/community.zammad.org/foss4ever/32/10629_2.png) [@foss4ever](https://community.zammad.org/u/foss4ever)\
**Post date:** [April 2, 2025, 11:38am UTC](https://community.zammad.org/t/scheduler-run-now/14417/2 "2025-04-02T11:38:55Z")

</div>

Please implement an option to “run immediately” as this is essential for running ad-hoc jobs without the hassle and risk of creating a full fledged scheduled task.

Available options could be:

Run immediately, then deactivate the scheduled task  
or  
Run immediately and skip creating scheduled task (ideal for ad-hoc job)

---

<div class="post-metadata">

**Author:** ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)\
**Post date:** [November 15, 2026, 2:41pm UTC](https://community.zammad.org/t/scheduler-run-now/14417/3 "2026-11-15T14:41:06Z")

</div>

It will be landing, soon™

> <https://github.com/zammad/zammad/issues/6455>
>
> As an admin, I want to run an existing scheduler job at the moment I decide to, …so that it acts on exactly the tickets I have just reviewed instead of whatever matches at its next time slot.
> 
> \## Use case scenarios
> \### Spam clean-up after review
> Sabine is the Zammad admin of a twenty-person support team at a mid-sized online retailer. Agents mark incoming junk as spam, and Sabine has a scheduler job that deletes spam tickets. Because agents occasionally mark a genuine customer request as spam by mistake, she keeps the job inactive and checks the matching tickets herself first. When she is satisfied, b is to activate it, set the
> next possible time slot, wait n remove the slot anddeactivate it again. In the meantime, new tickets may be marked as spam and get deleted without her having reviewed them, and if she forgets to clean up the schedule
> afterwards, the job keeps delets to start the job right after her review and to know when it has finished.
> 
> \## Acceptance criteria
> \- An admin can start a run of on demand, without changing its time slots.
> \- A run on demand is possible regardless of whether the job is active and whether it
> has any time slots configured.
> - Starting a run on demand does not change the job's active state or its schedule.
> \- The run starts without waiting for the next scheduler time slot.
> \- The admin can see that the rt has completed.
> \- A run on demand processes the job's conditions and actions the same way a scheduled run does.
> 
> \## Background information
> The original request comes from \[14417\](https://community.zammad.org/t/scheduler-run-now/14417). The scheduler checks jobs in
> ten-minute slots and skips a jt ten minutes or is stillmarked as running. A run on demand has to fit around both rules. The backend can
> already force a job to run outthing in the admin interfaceexposes that.
> 
> \## Possible solutions
> These are ideas, not decisionsion.
> \- A "Run now" button on the scnterface (the original title of
> this issue).
> 
> \## Clarification needed
> 1. What should happen when an he job is already running: is
> the request refused with an exred?
> 2. Should a run on demand affe for example by moving it back
> because the job ran just now?
> 3. Which admin interfaces does this need to cover: the current desktop view, the new
> desktop view, or both?
> \- A "Run now" button on the scnterface (the original title of
> this issue).
> 
> \## Clarification needed
> 1. What should happen when an admin starts a run while the job is already running: is
> the request refused with an exred?
> 2. Should a run on demand affect the next scheduled run, for example by moving it back because the job ran just now?
> 3. Which admin interfaces doesurrent desktop view, the newdesktop view, or both?
> 4. Should a run on demand be rmple in the job's history), soother admins can tell it was started manually?
