> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/intercept-studies/create-an-intercept-study/manage-duration-of-an-intercept-study.md).

# Manage duration of an intercept study

An intercept study can run for up to 90 days. However, you can customize the length if you want yours to end sooner.

{% hint style="info" %}
**Note:** Keep in mind that depending on your desired sample size, the specificity of your intercept URL, and any targeting attributes you’ve applied, you may benefit from a longer study duration to get the information you need.
{% endhint %}

{% stepper %}
{% step %}
Navigate to the **Overview** tab of your study.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/oiyG3Jzuy6wdDDVQKtrA/46244702291860)
{% endstep %}

{% step %}
Click anywhere in the **Study details** section.
{% endstep %}

{% step %}
In the **Ends after** field, enter the number of days you want your study to be open.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7zWgbLXQJtSBEuoZohAP/46244882866964)

{% hint style="info" %}
**Note:** Your study duration must be at least 1 day and may not be more than 90 days.
{% endhint %}
{% endstep %}

{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}

Now, your study duration is saved. Once you launch your study, it will automatically close after the number of days you’ve selected.

{% hint style="info" %}
**Note:** Your study will automatically close if you hit your designated participant limit, even if that occurs before your set study duration. Additionally, if you want to close your study early, you can do so manually. For more information, see [Close an intercept study](/intercept-studies/manage-an-intercept-study/close-an-intercept-study.md).
{% 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://help.dscout.com/intercept-studies/create-an-intercept-study/manage-duration-of-an-intercept-study.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.