> For the complete documentation index, see [llms.txt](https://glowie-app.gitbook.io/glowie-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glowie-app.gitbook.io/glowie-docs/resources/advanced-settings.md).

# Advanced Settings

### 🔧 Advanced Settings (Proxy and Task Control)

This setting gives you full control over how resources like proxies and tasks are utilized in each module. By default, most fields will be set to **1000**, meaning there are virtually no restrictions. But if you want to fine-tune how often a single proxy is used or how many lines to pull from a file or database, this is the section for you.

***

### **🧠 Why Use It?**

If you’re running into rate limits, bans, or simply want better distribution of tasks across your proxies or data, these settings allow precision-level control.

***

### **⚙️ How to Enable Advanced Settings**

1. Navigate to the **top of your module**
2. Click: `Settings → Show Advanced`

***

### **✏️ How to Adjust Based on Input Method**

* **Using a Text File**\
  Make sure to adjust the value under: `LinesFromFile`
* **Using a Database**\
  Ensure the input source is set correctly to: `Database`


---

# 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://glowie-app.gitbook.io/glowie-docs/resources/advanced-settings.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.