> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/tips-and-tricks/avo-assure-client.md).
# Avo Assure Client
Use this section for effectively using the client settings in Avo Assure. These suggestions help you to ensure smooth communication between the server and client machine and optimize overall test execution performance.
Configure the Global Time-Out for Stable Test Execution
Increase the **Global Time-Out** value in **Avo Assure Client Settings** to slightly exceed your application's average response time to prevent false test failures caused by temporary network or server delays.
Clear Stale Browser Processes Before Execution
Use the **Kill Stale Process** option in the **Avo Assure Client** before starting a new execution to close leftover browser processes and ensure a clean execution environment.
Use Stepwise Debugging to Isolate Test Failures
Use **Stepwise Debugging** to execute test steps one at a time, making it easier to identify failing steps, validate object interactions, and troubleshoot synchronization or timing issues efficiently.
---
# 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://docs.avoautomation.com/avo-assure/support-resources/tips-and-tricks/avo-assure-client.md?ask=&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.