tinyhumansai/openhuman · error

[core-state] memory client sync failed during refresh:

Error message

[core-state] memory client sync failed during refresh:

What it means

Syncing the memory client's auth token failed during a core-state refresh: syncMemoryClientToken rejected while applying a new snapshot.sessionToken to the memory client (whose token differed from memoryTokenRef). The refresh continues past the failure, but memory operations (sync, search) may run unauthenticated or fail until the next refresh tick retries the sync.

Source

Thrown at app/src/providers/CoreStateProvider.tsx:464

      // the token it was authed with has been invalidated by the core.
      socketService.disconnect();
    }
    // Same-user re-login (seedUserId === nextIdentity) and cold bootstrap
    // with matching seed are no-ops — redux-persist already loaded the
    // right namespace and the active user id is already correct.
    syncAnalyticsConsent(snapshot.analyticsEnabled);

    if (!snapshot.sessionToken) {
      memoryTokenRef.current = null;
      return;
    }

    if (memoryTokenRef.current !== snapshot.sessionToken) {
      try {
        await syncMemoryClientToken(snapshot.sessionToken);
        memoryTokenRef.current = snapshot.sessionToken;
      } catch (error) {
        console.warn('[core-state] memory client sync failed during refresh:', error);
      }
    }
  }, [commitState, t]);

  /** Serialized refresh — all callers share the same in-flight promise. */
  const refresh = useCallback(async () => {
    if (refreshInFlightRef.current) {
      return refreshInFlightRef.current;
    }
    const promise = refreshCore().finally(() => {
      refreshInFlightRef.current = null;
    });
    refreshInFlightRef.current = promise;
    return promise;
  }, [refreshCore]);

  const refreshTeams = useCallback(async () => {
    const requestId = ++teamsRequestIdRef.current;

View on GitHub (pinned to 7491200858)

Solutions

1. Check the warned error for the sync layer — memory client connect or token apply
2. Rely on the next refresh cycle to re-attempt the token sync automatically
3. If memory features fail in the UI (search/sync errors), confirm the core memory service is healthy
4. Persistent failures: inspect the memory client logs for auth rejection reasons

When it happens

Trigger: Thrown at app/src/providers/CoreStateProvider.tsx:464 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17). Data as JSON: /api/errors/cb2d60babfe287a4. Report an issue: GitHub.