> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rokroyalty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix common Vanguard issues, refused actions, and attachment errors

> Fix attachment errors, license problems, missing actions, and refused reasons in Vanguard's Activity Log. Contact support with your log attached when you need help.

When Vanguard is not behaving the way you expect, the quickest way to find out why is the **Activity Log** page. Every action Vanguard sends, and every reply the game returns, is written there in plain language. This page covers the most common problems, what a **refused** verdict means, and how to collect information for support.

For issues with Vanguard Hub (headless multi-account mode), see the [Hub troubleshooting guide](/vanguard/hub/troubleshooting).

> **"Could not attach" or the dot never turns green**
>
> Vanguard must be running **as administrator**. Approve the UAC prompt when it opens, or right-click the .exe and choose **Run as administrator**. The game must be open and logged in, and no other tool may be attached to it. On **Settings**, make sure **Game connection** is set to **PC** if you play the PC client, or **Emulator** if you play in an Android emulator.

> **The top bar says NOT LICENSED**
>
> Go to **License** and paste your key, then press **Activate**. If it says the key has expired, paste a renewed key. To get one, press **Contact us** and pick **Billing & licenses**. A full Vanguard key also works in Vanguard Farm. A Vanguard Farm key or a Vanguard Hub key will not work in the other app.

> **The loop is running but nothing happens**
>
> Check three things:
>
> 1. The pill: in **DRY-RUN** nothing is sent.
> 2. The function toggle: the feature's card must be switched on.
> 3. The rest window: open **Settings** and check whether a **resting now** badge is showing. If it is, Vanguard is paused until the rest window ends.
>
> Then open the **Activity Log** and look for **refused** lines. They say why the game declined the action.

> **A limit or cooldown is wrong for my kingdom**
>
> Change it yourself. Open the relevant feature card, expand **Settings ▾** (or **Advanced** inside it, shown when **Expert mode** is on in **Settings**), and type the new number. For gather-specific limits, use the **Gather** card settings. The new value applies on the next pass. No update is needed. The undo arrow next to any value you changed puts it back to the built-in default.

> **It sent a combat commander to gather**
>
> **Gathering commanders only** is switched off. With it off, Vanguard ranks every idle commander and sends the best two, whoever they are. Switch it back on in the **Gather** card's **Settings ▾**. Switching it off asks you to tap twice on purpose.

> **Gather says there are no free marches when there are**
>
> Vanguard learned a march limit from an earlier refusal. On the **Gather** card, press **re-learn** next to the march slot limit. The game will set the correct limit again the next time it matters.

> **I pressed Stop and it kept going for a moment**
>
> **Stop** ends the loop as soon as the chore that is running finishes. The chores still waiting in that round do not run. If the running chore is waiting on the game (a long march search, for example), it can take a little longer. Press **Detach** afterwards if you want the game fully disconnected.

> **I changed a setting. Does the running loop pick it up?**
>
> Yes. Resources, gather settings, pacing, timing randomness, the rest window and **DRY-RUN/LIVE** all apply on the next pass. Switching a feature on or off applies straight away.

> **Running two accounts (two games open)**
>
> Each Vanguard drives exactly one game. Make a second copy of the whole Vanguard folder (it keeps its own settings and learned files) and give it its own license key, open the second game, then in each Vanguard go to **Settings** and use the **Game instance** picker to choose which game that copy should drive. If the second game runs inside a sandbox such as Sandboxie, the Vanguard for it must be started **inside the same sandbox**. A program outside the sandbox is not allowed to connect to a program inside it.

> **The game crashed or was restarted**
>
> Press **Stop**, then **Detach**, restart the game and log in, then **Attach to game** again and press **Start Loop**. Vanguard does not re-attach on its own after a crash.

> **My hub account stopped and says the license was lost**
>
> Vanguard checks in with the license server to keep one running copy per key. If the same key is started on another PC, the first copy loses it and stops. The hub logs every account out when this happens. Close the other copy, then start the hub again. See [License](/vanguard/getting-started/license) for how the online check works.

## Understanding refused actions in the Activity Log

When the game declines a request, the **Activity Log** shows a **refused** badge and a plain-English reason. The most common ones are:

| Refused reason | What it means |
| - | - |
| chest already opened | The daily chest or quest reward was already collected. |
| chest not unlocked yet | Your activity score is not high enough for that chest. |
| march limit reached | All march slots are full; Vanguard may need to re-learn the limit. |
| not enough action points | Your account does not have enough AP for barbarians or fort rallies. |
| can't remove the rally leader | Vanguard tried to trim a rally but cannot remove the captain. |
| nothing training there | The training building is idle or already collected. |
| nothing healing there | The hospital is empty or already collected. |
| you don't have that item | The item needed (speed-up, shield, action point item) is not in your bag. |
| not enough resources | A build or train request failed because a resource is missing. |

> [!NOTE]
>
> A refused action is not always a bug. The tavern draw returning "not ready yet" or a chest being "already opened" simply means the game is not ready, and Vanguard will try again later.

## Contact support with your log

The quickest way to get help is **Contact us** at the bottom of the sidebar. Pick a topic, describe what you expected and what happened, and leave **Attach my activity log** ticked. Vanguard sends the log for you, so there is nothing to find or attach. See [Contact us](/vanguard/app/overview#contact-us).

To keep a copy of the log yourself, open the **Activity Log** page and press **Export log**. Vanguard saves the full log as a text file wherever you choose.

> [!WARNING]
>
> The log contains your governor name, city coordinates, and alliance tags. It never contains your password or your license key. Only share an exported log with people you trust.

## Still stuck?

If none of the items above matches your problem, run one more **DRY-RUN** pass, then press **Contact us** with **Attach my activity log** ticked. Say whether the top bar was in **DRY-RUN** or **LIVE** at the time.

For issues related to the headless multi-account Hub, see [Hub troubleshooting](/vanguard/hub/troubleshooting).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.