> For the complete documentation index, see [llms.txt](https://docs.mobb.ai/mobb-user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobb.ai/mobb-user-docs/common-troubleshooting-scenarios/broker-rotated-still-failing.md).

# Broker & Tokens - Rotated token but still failing

{% hint style="warning" %}
This scenario applies **only to on-premises deployments** that use the [Mobb Broker](/mobb-user-docs/more-info/mobb-broker.md).
{% endhint %}

**Symptoms**

* You generated a new broker token, but Mobb's logs still show broker connectivity errors.
* Mobb still appears to be using the old token.

**Likely cause**

Generating a new token is only half of the rotation. The **running broker container must be restarted (or its environment updated)** so it picks up the new `FRP_BROKER_AUTH_TOKEN` value. Until then, the broker client keeps presenting the old token.

**Resolution**

1. Update `FRP_BROKER_AUTH_TOKEN` with the new value wherever your broker runs (for example, the container's environment variables — on AWS ECS this is the task definition).
2. **Restart the broker** so the new token takes effect. On ECS, force a new deployment / restart the task so it reads the updated variable.
3. Confirm every broker client is updated if you run more than one (each SCM/domain may have its own broker).

See the environment-variable reference in the [Mobb Broker guide](/mobb-user-docs/more-info/mobb-broker.md#explanation-of-the-environment-variables).

{% hint style="info" %}
Still stuck? Contact <support@mobb.ai>.
{% endhint %}