> 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/programs-and-rules/conditions/time-conditions.md).

# Time Conditions

Defining when a rule is active

## **Overview**

**Active Dates**

Time conditions restricts the operation of a rule or program to defined dates and/or times.

Only activity done, transactions made, or goals that are satisfied, within the specified active time period will cause the rule to successfully be evaluated. For example, if a sales rule is only active between June 15th and June 21st, sales made outside this period will not cause the rule to execute. 

**Time Zones**

It's important that you configure the timezone to ensure this condition applies to the correct dates and times. If you wish to create programs or rules across multiple timezones, you'll need to create individual rules for each timezone. 

**Active dates versus trigger-level time conditions**

Active dates simply specify when a program or rule will take effect. If you wish to set dates or times in which an activity will create a trigger or goal to evaluate, set a Qualifying Time when creating a trigger such as an Action or Goal. 

<br>

<br>


---

# 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/programs-and-rules/conditions/time-conditions.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.