> 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/frequently-asked-questions/how-does-copystorm-jobrunner-recover-from-a-system-reboot.md).

# How Does CopyStorm/JobRunner Recover from a System Reboot?

When a system crashes, is rebooted, or if the CopyStorm/JobRunner application is manually terminated; the CopyStorm/Director database will contain data indicating that jobs are running when they were terminated unexpectedly. This article explains how CopyStorm/JobRunner recovers from this situation.

The answer is that all of these cases are handled the same way:

* Each time CopyStorm/JobRunner starts a task, the system process id of the task is stored in the CopyStorm/Director database.
* Each time CopyStorm/JobRunner starts it looks for tasks configured as running in the CopyStorm/Director database which have disappeared from the system.
  * If found, the jobs are marked as completed and given a log file status of “Process died without notifying Copystorm/Director.”
* Any job detected as dying unexpectedly is rescheduled using the job’s scheduling parameters.

When job completion is detected using this approach the CopyStorm/Director database may indicate that the last status of an unusually high number of jobs was “Error”. This is likely to happen if a job was terminated during a reboot and will be recovered from automatically the next time the job is scheduled.


---

# 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/frequently-asked-questions/how-does-copystorm-jobrunner-recover-from-a-system-reboot.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.