> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/vault/vault-features/reporting/stale-jobs.md).
# Stale Jobs
## Preventing Stale Jobs
### Overview
The **Stale Jobs** feature in AutoRABIT Vault enables administrators to monitor and manage jobs that have stalled during execution. Any job that remains inactive—i.e., without backend file updates—for **four consecutive days** is flagged as a *Stale Job*.
***
### Introduction
AutoRABIT Vault manages stale jobs using a two-pronged approach:
1. **Automated Cron Job**: Scheduled weekly to identify and terminate long-running inactive jobs.
2. **Stale Jobs Interface**: Allows admins to manually view, select, and terminate stale jobs.
Key behaviors:
* Admins can manually terminate one or more stale jobs.
* For a single job, a **termination notification** is sent to both the admin and the job creator.
* For multiple jobs, a **consolidated notification** is delivered.
***
### How to Access the Stale Jobs Module
1. **Select the target Org** from the list of available organizations.
2. A list of jobs from various modules (Backup, Restore, Replicate, Archive) will be displayed for the selected Org.
3. Navigate between module tabs to review stale jobs in each category:
* **Backup Jobs**
* **Restore Jobs**
* **Replicate Jobs**
* **Archive Jobs**
***
### Terminating Stale Jobs
4. Select the jobs you wish to terminate and click **Terminate**.
5. **Notifications:**
* **Single Job Termination**:
* An email is sent from the relevant module.
* The message includes a new field: `Terminate Reason`.
* **Multiple Job Termination**:
* A consolidated email lists all terminated jobs.
This feature ensures system hygiene and prevents inactive jobs from consuming unnecessary system resources.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledgebase.autorabit.com/product-guides/vault/vault-features/reporting/stale-jobs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
