# SYNC_ACCOUNT_CHANGED

<!-- Generated by docs/modules/diagnostics from the package catalogs. Write a guide in docs/diagnostics/<CODE>.md instead of editing this file. -->

The push had writes of another account, such as after a sign-in as another person in another tab. The server wrote nothing. The client keeps the writes in IndexedDB, pulls the rows of the new account, and sends the writes when their account signs in again. They are not in `rows`, `queued`, or `failures` meanwhile. `clearSync()` drops them. A push of the same account after a team change is not refused: it applies under the current `where`.

## Source

`SYNC_ACCOUNT_CHANGED` belongs to the `sync` package. Its catalog entry is in [`src/errors.ts`](https://github.com/vite-hub/vitehub/blob/main/packages/sync/src/errors.ts#L17). It is raised in [`src/handler.ts`](https://github.com/vite-hub/vitehub/blob/main/packages/sync/src/handler.ts#L1062).

See [all Sync diagnostics](https://vitehub.dev/docs/sync/diagnostics).

<!-- vitehub-docs:section-links -->
## In this section

- [Overview](https://vitehub.dev/raw/docs/sync.md)
- [Get started](https://vitehub.dev/raw/docs/sync/get-started.md)
- [Server API](https://vitehub.dev/raw/docs/sync/server-api.md)
- [Limits and errors](https://vitehub.dev/raw/docs/sync/limits-and-errors.md)
- [Vue](https://vitehub.dev/raw/docs/sync/vue.md)

Next: [SYNC_ACTION_REFUSED](https://vitehub.dev/raw/docs/sync/diagnostics/sync_action_refused.md)

All pages: [llms.txt](https://vitehub.dev/llms.txt)
