# Reconnect failed after skip or disconnect

Reconnect failures often mean old waiting records were not fully cleared before a new match attempt.

- Canonical URL: https://personapp.io/help/technical-support/reconnect-failed
- Category: Technical Support
- Platforms: web, ios, android
- Published: 2026-02-21
- Last reviewed: 2026-02-25
- Publisher: PersonApp Help Center (https://personapp.io/help)

---

After disconnect or skip, PersonApp runs cleanup before re-entering queue. If reconnect fails, forcing a full session reset usually clears stale token/room state and restores matching.

## Steps

1. Leave the current screen, then return and start a fresh match request.
2. Wait a few seconds after skip so cleanup completes before next connect.
3. Refresh browser tab if token/room state looks stuck.
4. If repeated, sign out/in and retry to ensure session token is fresh.

## Frequently Asked Questions

### Why does reconnect fail right after multiple skips?

Rapid consecutive skips can outpace cleanup timing and leave temporary stale state.

### Does reconnect failure mean I was banned?

Not necessarily. Ban state is handled separately and would show a dedicated suspension screen.

---

*Markdown version of https://personapp.io/help/technical-support/reconnect-failed, provided for AI assistants and plain-text readers. Full index: https://personapp.io/llms.txt*