> For the complete documentation index, see [llms.txt](https://learn.capstorm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.capstorm.com/copystorm-director/reference/copystorm-jobrunner/force-a-job-to-run-on-demand.md).

# Force a Job to Run On Demand

Forcing a specific CopyStorm job to run on demand requires three things:

* Database credentials for the CopyStorm/Director database.
* The unique integer Job Number for the job containing the task to run.
* The family to which the job belongs.

All of this data is visible when viewing a job in the CopyStorm/Director GUI:

![](/files/Z0ZLgPMnuD4XyyOhwMwX)

With this information, the following command line will force the corresponding CopyStorm job to run immediately:

* Windows:
  * CopyStormJobRunner.bat -action runCopyStorm -jobs 1 -family Default -cscredentials “encrypted-credentials-string”
* Linux/Mac:
  * sh CopyStormJobRunner.sh -action runCopyStorm -jobs 1 -family Default -cscredentials “encrypted-credentials-string”

If the job is a CopyStorm/Medic task, change the -action argument to CopyStormMedic:

* Windows:
  * CopyStormJobRunner.bat -action runCopyMedic -jobs 1 -family Default -cscredentials “encrypted-credentials-string”
* Linux/Mac:
  * sh CopyStormJobRunner.sh -action runCopyMedic -jobs 1 -family Default -cscredentials “encrypted-credentials-string”

The log file and status of the run will be stored in the CopyStorm/Director database — just as if the CopyStorm/JobRunner were invoked from a scheduler.

CopyStorm/JobRunner will output information similar to the following example:

![](/files/AqUgoQAtK5pdpTieIOMg)

Only a single task in a job can be forced to run on demand at the same time. See the [CopyStorm/JobRunner command line options](/copystorm-director/reference/copystorm-jobrunner/command-line-options.md) for more details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.capstorm.com/copystorm-director/reference/copystorm-jobrunner/force-a-job-to-run-on-demand.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.