> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/samples/sample-projects/miscellaneous/scheduled-system-maintenance.md).

# Scheduled System Maintenance

This sample project demonstrates how to use the PurgeLogEntries activity from the Automation module to clean up and maintain your project.  To automate the process the project has been scheduled to run every 24 hours.

**Activities:**

The project contains only a single activity - the PurgeLogEntries activity from the Automation module.  

Edit the activity and notice that it has a single property.  Enter the value of the number of days to be used for purging logging records.  That's all that is required.

## **appRules Scheduler**

This project has been scheduled to be run by the appRules Scheduler.   The workflow details shows the scheduling configuration in the Schedule tab:

{% hint style="info" %}
You can select one of the preconfigured run frequencies or configure a new one using the Cron syntax.
{% endhint %}


---

# 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://docs.appstrategy.com/apprules-r-documentation/samples/sample-projects/miscellaneous/scheduled-system-maintenance.md?ask=<question>&goal=<user_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.