> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/studio/ui-elements/loader/trouble-shoot.md).

# Trouble Shoot

<details>

<summary>How do I wait for the loader</summary>

Loader can be configured in 2 ways as explained. Link to the refence.[loader](/studio/ui-elements/loader.md#automation)

</details>

<details>

<summary>How do I inspect the loader</summary>

In the daily applications we see different types of loaders and their behavior completely depends on the time taken for the page to load.

Open the developers tools in the browser and navigate to source tab. PAUSE the browser when you see a loader\
Now sit back inspect the element and write the locator.

</details>

<details>

<summary>I don't have / see a loader on my webpage</summary>

In the modern application, we definitely see a element that will dissappear after loading the content of the page. \
If, there was no such elements in our web page. We need to skip thinking about the loader and validate the header of the page to continue further

</details>

<details>

<summary>What was the maximum time I can wait for the loader</summary>

Usually, we can wait for the maximum of 2 minutes for a loader and completely depends on the network conditions and multiple factors.

</details>

<details>

<summary>I couldn't inspect my loader. It was fast as rocket</summary>

Yes, we do see this kind of situations where a loader is disappeared in a fraction of milli seconds. Pausing the script and inspection was the only way we can do it.

</details>

<details>

<summary>I have multiple loaders in my application, How can i handle them</summary>

Yes, this is pretty simple in QATTS. this can be done in either of ways in action class / action.

Ex : action.pre : waitforloader:UI\_Element

</details>

<details>

<summary>Sometimes my loader appears and sometimes not. How does this work</summary>

Yes, As said we might not get the loaders all the time. QATTS has an internal mechanism when the loader is not found in 2 seconds. It just skips and proceeds with the next steps in action.

</details>

<details>

<summary>Timeout exception in the task when loader appears</summary>

This happens when the loader time is greater than the given maximum time of the UI element. increasing the time will solve the problem

</details>