# Troubleshooting Guide

### ⏱️ I created my gauge, but it is not visible yet

Your gauge may take up to 24 hours to fully come online.<br>

***

### 🧩 I bought votes but do not see any delta

#### Possible causes

**Wrong epoch timing**

* Check whether the new voting epoch has started at\
  <https://tribeca.so/gov/vault/gauges>
* Votes purchased apply to the next epoch, not the current one. Wait for the epoch rollover before expecting a delta.

**Not enough time has passed**

* Deltas typically appear within three hours after the epoch begins. Allow up to six hours before assuming there is an issue. Continue checking\
  <https://thevault.finance/validators>

**Wrong validator selected**

* Confirm that votes were purchased for the correct validator address. Review your Votex transaction history for verification.

**Solution**

Wait for the epoch to begin, then check for your delta within three to six hours.

***

### ⏳ I see a delta but no stake on my validator

This is expected behavior.

#### What the delta means

* A visible delta indicates that your validator is in the priority queue. Stakebot processes this queue over time, prioritizing gauge stake over undirected stake. First time or large stake movements may take slightly longer.

#### Timeline expectations

* Typical distribution completes within six to eight days.
* First time participants may experience slightly longer delays.
* Repeat participants usually see faster redistribution.

#### What to verify

* Confirm the delta appears at\
  <https://thevault.finance/validators>
* Stakebot runs every three hours.
* Gauge stake is treated as high priority.

**Solution**

Remain patient and monitor your validator page for updates.

***

### 🚪 Vote buying window is closed on Votex

#### Why this happens

* Voting closes on the final day of each voting epoch. This allows votes to be finalized before the next epoch begins.

#### What to do

* Check the next epoch start time at\
  <https://tribeca.so/gov/vault/gauges>
* Wait for the new epoch to begin.
* The voting window will reopen and remain open for six days.

**Tip**

Buying votes closes on the 6th day. Buying votes early in the epoch helps avoid missing the window.

***

### 📉 I only voted for one week and returns were minimal

#### Why this occurs

* Gauge impact compounds over time.
* Week one establishes voting position.
* Week two delivers full impact.
* Week three provides optimal sustained results.

#### Recommended approach

* Commit to two or three consecutive weeks.
* Plan budget across multiple epochs.
* Evaluate ROI over multiple weeks rather than a single epoch.

#### Planning formula

```
Minimum investment = Weekly vote cost × 3
Expected return = Stake × Commission × APY × 3 ÷ 52
```

***

### 🔄 Stake disappeared after the epoch ended

#### Possible causes

* Votes were not renewed for the next epoch.
* Gauge votes last only one week.
* Other validators outbid your voting power.
* Stakebot rebalanced stake due to delta changes.

#### Solution

Buy votes consistently every epoch to maintain gauge stake.

***

### 🗓️ Unsure when to buy votes

There are two different systems involved.

Solana epochs last roughly two to three days and are not relevant for gauges.\
Voting epochs last seven days and determine gauge behavior.

#### Clear sequence

* Check the current voting epoch at\
  <https://tribeca.so/gov/vault/gauges>
* Buy votes during the six day open window.
* Votes apply to the next voting epoch.
* Deltas appear within three hours of the new epoch start.
* Stake distributes gradually over that epoch.

#### Example

Votes purchased during Epoch 20 apply to Epoch 21. Delta appears when Epoch 21 begins and stake is distributed over the following days.

***

### 👛 Wallet confusion

Wallet choice does not matter.

* Any wallet can be used.
* Different wallets may be used each week.
* Only the validator address and amount spent are relevant.

***

### 📊 ROI uncertainty

#### How to estimate returns

```
Voting power = Your spend ÷ Total epoch spend
Expected stake = Total pool stake × Voting power
```

```
Weekly earnings = Stake × APY ÷ 52 × Commission
Weekly cost = Vote spend
```

Evaluate performance across two to three weeks for accuracy.

***

### 🚫 Validator not showing as eligible

#### Minimum requirements

* Acceptable commission rates.
* Strong uptime and performance.
* Compliance with The Vault baseline standards.

**Some segments require board review, while gauge participation itself is permissionless.**

#### Solution

Verify validator metrics and contact The Vault team if eligibility appears incorrect.

***

### 🖥️ Dashboards not updating

#### Common causes

* Cached data in the browser. Perform a hard refresh.
* Data synchronization delays across analytics sources.
* Stakebot has not run yet.

#### Solution

Wait three to six hours and recheck after refreshing.

***

### 🐢 Gauge stake taking longer than expected

#### Possible reasons

* Initial large stake movements.
* High queue volume.
* Gradual redistribution designed to protect APY.

#### Expected indicators

* Delta visible on dashboard.
* Gradual stake increases over time.
* Full allocation by the end of the epoch or shortly after.

**Solution**\
Continue voting weekly. Distribution speed improves in future epochs.

***

### 🆘 Still Stuck?

Review the [Votex Quick Start Guide](https://docs.thevault.finance/gauges/votex-quick-start-guide) and [Gauges page](https://docs.thevault.finance/about/gauges). If needed, contact Discord support with the following information.

* Validator address
* Epoch number
* Transaction hash if available
* Relevant screenshots

The team is available to help.


---

# 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.thevault.finance/gauges/troubleshooting-guide.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.
