> For the complete documentation index, see [llms.txt](https://renkogurus.gitbook.io/renkogurus-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://renkogurus.gitbook.io/renkogurus-documentation/renkogurus-propbot-user-guide/vps-prop-bot/renkogurus-vps-dashoard/bot-status-panel.md).

# Bot Status Panel

<figure><img src="https://273289729-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXlGDI9rakMRwrwFoVorR%2Fuploads%2FfrQBXjRcYVE5c5NuTHBc%2FScreen%20Shot%202025-05-04%20at%209.53.14%20AM.png?alt=media&amp;token=ca375080-ebd1-4a78-aab7-010e10122cf3" alt=""><figcaption></figcaption></figure>

### Bot Status Panel

The **Bot Status** panel provides real-time information about the current operational state of your VPS Bot instance. This is essential for understanding whether your bot is ready to accept and execute commands, as well as for verifying webhook setup and system health.

***

#### 📋 Status Indicators

| **Field**        | **Description**                                                                                                                                                                          |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Status**       | Indicates the current operational mode of the bot. Possible values: `Idle`, `Executing`, or `Error`. If `Idle`, the bot is awaiting commands.                                            |
| **Uptime**       | Shows the duration (in `hours:minutes:seconds`) for which the bot has been running since the last launch or reboot. Useful for monitoring session stability.                             |
| **Current Time** | Displays both **Local Time** (based on VPS timezone) and **UTC Time**. This helps ensure correct synchronization of trade alerts and webhook triggers, especially across global markets. |
| **AWS Webhook**  | This is the endpoint that receives webhook signals from TradingView or other sources. It triggers trades or actions based on incoming alert payloads.                                    |

***

#### 🌐 AWS Webhook Setup

> ⚠️ **Important Note**: The AWS Webhook URL is **pre-configured** and securely hosted by the RenkoGurus team.\
> ✅ **You do not need to modify or set this yourself.**\
> Your only task is to copy this URL and paste it into your TradingView **alert webhook field** to connect signals to the bot.

**Webhook Usage Example in TradingView:**

* Go to your indicator’s alert setup
* In the “Webhook URL” field, paste the full AWS Webhook URL  and the payload to place orders
* Example:\
  `https://XXXX.execute-api.us-east-1.amazonaws.com/PROD/buy`

This will ensure TradingView alerts are sent directly to your bot in real-time.

***

#### 🧠 Best Practices

* Check the **Status** before triggering alerts to ensure the bot is not paused or erroring.
* Monitor the **Uptime** periodically if you are running a multi-session or multi-day strategy.
* Use the **Current Time** to validate alignment with your configured **Trading Hours (GMT)**.
* Double-check the **Webhook URL** in TradingView if you notice signals not executing — any typo will result in dropped alerts.