# Account Status System

## Bot Cycle

Bots work in a cycle where all steps are repeated in a loop, as follows:

<mark style="color:red;">**\[1]**</mark> <mark style="color:red;"></mark><mark style="color:red;">Bot asks for acount ></mark> <mark style="color:red;"></mark><mark style="color:red;">**\[2]**</mark> <mark style="color:red;"></mark><mark style="color:red;">Gets account and tries logging in to League ></mark> <mark style="color:red;"></mark><mark style="color:red;">**\[3]**</mark> <mark style="color:red;"></mark><mark style="color:red;">Checks if quota is met on the account ></mark> <mark style="color:red;"></mark><mark style="color:red;">**\[4]**</mark> <mark style="color:red;"></mark><mark style="color:red;">Checks for possible actions issued (turn-off-vm, pause, etc) ></mark> <mark style="color:red;"></mark><mark style="color:red;">**\[5]**</mark> <mark style="color:red;"></mark><mark style="color:red;">Start a match > Go to step</mark> <mark style="color:red;"></mark><mark style="color:red;">**\[3]**</mark>

This loop only works if the virtual machine using the account is working, that is why if you try using an action and the bot isn't actively using the account (bot might be closed or broken), the action will never be completed since the cycle is not happening and actions are only performed when the bot reaches the step **\[4].** At this point if you want to for example make the account offline, you need to wait until the system automatically sets it to status **"offline"** and **not active**.

## Auto-offline system

Every *5 minutes* the system will check all accounts, if their **"Active"** field is *true,* and the latest update was more than 35 minutes ago, it will set these accounts to **"Active"** field *false* and status **offline**, effectively "fixing" them as no bot is currently using them.

{% hint style="warning" %}
Using actions (turn-off-vm, pause, restart, etc) will reset the *35 minutes* timer, making you wait the time until it is set to inactive. Be patient when an account is left as active but no bot instance is using it, it will eventually be resolved.
{% endhint %}

#### Some common causes for an account to be left Active but no bot using it are:

* Turning Off a virtual machine without using the dashboard actions with the bot running.
* Clicking the <mark style="color:red;">**X**</mark> icon in the CMD window in the bot program too many times (not allowing it to close itself and set current account offline correctly, click once and wait until the CMD is closed)&#x20;

![](/files/6FOGy5oXdT18CwdJT8YR)

{% hint style="info" %}
If the account status is **"ingame"** at the time of clicking the <mark style="color:red;">**X**</mark>, it will not be set to offline so when you open the program again, bot will enter the same game and finish it.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gydrus.net/general-information/account-status-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.