> 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/troubleshooting-guides/design-studio/execution/executing-test-cases-from-queued-state.md).

# Executing Test Cases from Queued State

| Unable to execute test cases from the Execution List. Test cases remain in a queued state and do not start execution. | <ul><li>Version mismatch between the Avo Assure client and the server instance</li><li>Test cases stuck in the execution queue</li><li>Network connectivity issues affecting execution</li></ul><p>.</p> | <ul><li>Ensure that the Avo Assure client version matches the server instance. If there is a mismatch, update the client to the latest version, relaunch it, and retry execution.</li><li>If any test cases are stuck in the queue, terminate them and restart the execution.</li><li>Verify network connectivity and ensure there are no interruptions affecting execution.</li><li>After performing the above steps, re-initiate the execution from the Execution List.</li></ul> |
| --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


---

# 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/troubleshooting-guides/design-studio/execution/executing-test-cases-from-queued-state.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.
