> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2022-roc-open-mics/august-26th-2022-data-retention-and-cron-jobs.md).

# August 26, 2022 - Data retention & Cron Jobs

In this call, we're going to talk about our latest feature around data retention within Rewst and how you can configure results to be removed after x number of days

We're also going to talk about some new triggers, including our new Cron Job trigger so you can run workflows at the same time, on your own schedule.

Finally, we'll finish with a Live Q\&A about all the things you want to know!

{% embed url="<https://www.youtube.com/embed/MozDSyuR-Hw>" %}

## Contents of the recording

<details>

<summary><strong>Contents of the Call</strong></summary>

This call is for people who are interested in building their own workflows. We will talk about the platform, news, some training, and any Q\&A. As always, feel free to unmute and interrupt us, this is an interactive call!

</details>

<details>

<summary><strong>How to get help from the ROC</strong></summary>

How to get help - Engage the ROC in Slack - Email support coming soon! - \[FUTURE] Live chat in the app - Would this be helpful to people? - Documentation - <https://rewst.help> - Feature Requests - <https://rewst.canny.io/>

</details>

<details>

<summary><strong>Updates for the week</strong></summary>

</details>

<details>

<summary><strong>Learning Topic</strong></summary>

* Cron Job Triggers

</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2022-roc-open-mics/august-26th-2022-data-retention-and-cron-jobs.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.