> For the complete documentation index, see [llms.txt](https://village-labs.gitbook.io/coworker-product-and-developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://village-labs.gitbook.io/coworker-product-and-developer-docs/legacy-knowledge-base/awards/award-expiration.md).

# Award Expiration

Different ways awards expire

## Overview

Both Non-Monetary Awards, as well as Badges & Statuses, can have optional expiration periods, either rolling, bulk or both.

* **Rolling expiration** means any award issued expires a defined number of days after issuance. For example, if a user has 1,000 Star Points with a 30-day rolling expiration window, each point will expire 30 days after it was received.&#x20;
* **Bulk expiration** means all awards of this type held by a user expire after a defined number of days of non-activity on the platform. For example, if a user has accumulated $100 'Orange Credits' with a 30 day bulk expiration period, these will all expire if the user is inactive for 30 days, irrespective of when the user received them.&#x20;
* Both types of expiration period can be applied to the same award.


---

# 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://village-labs.gitbook.io/coworker-product-and-developer-docs/legacy-knowledge-base/awards/award-expiration.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.
