> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/back-in-stock-notification/scheduled-tasks.md).

# Scheduled Tasks

The Stock Reminder plugin uses two scheduled tasks that run automatically in the background.

## Notification Task

This task regularly checks whether products with active subscriptions are available again. As soon as a product meets the notification condition (default: stock greater than 0), notification emails are sent to all subscribers of that product.

Emails are sent via the Shopware Flow Builder. The email templates can be customized there at any time.

After sending, the subscription status is set to "notified".

## Cleanup Task

This task automatically deletes old subscription entries that have already been notified. The retention period is controlled via the "Delete old subscription entries after (days)" configuration setting (default: 30 days).

If the value is set to 0, no automatic cleanup is performed.

{% hint style="info" %}
The scheduled tasks are executed through the Shopware Scheduled Task system. Make sure that the cronjob is correctly set up in your Shopware environment so that the tasks run reliably.
{% 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 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://docs.premsoft.de/en/plugins/back-in-stock-notification/scheduled-tasks.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.