> 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/test-case/enabling-button-during-automation.md).

# Enabling Button during Automation

| Problem                                      | Cause                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Instructions to Resolve                                                                                                                                                                                                                                                                                    |
| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The button is not enabling during automation | <ul><li>The entered value may not be properly saved or committed, so the system does not recognize the update.</li><li>There could be a timing issue where the application has not finished processing the input before the next step is executed.</li><li>If the input value is invalid or incorrect, the expected action may not be triggered.</li><li>Some fields require user-like interaction (such as keystrokes) rather than direct value entry to work correctly.</li></ul> | <ul><li>Ensure that valid input values are provided.</li><li>Use the Set Text (directly sets the field value) action to enter the value.</li><li>If the issue persists, switch to Send Keystroke (Enters the value character by character) value action to ensure the input is properly entered.</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/test-case/enabling-button-during-automation.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.