thedotmack/claude-mem · error
Failed to load ${dataType}: ${response.statusText}
Error message
Failed to load ${dataType}: ${response.statusText} What it means
Error "Failed to load ${dataType}: ${response.statusText}" thrown in thedotmack/claude-mem.
Source
Thrown at src/ui/viewer/hooks/usePagination.ts:55
return [];
}
stateRef.current = { ...stateRef.current, isLoading: true };
setState(prev => ({ ...prev, isLoading: true }));
const params = new URLSearchParams({
offset: offsetRef.current.toString(),
limit: UI.PAGINATION_PAGE_SIZE.toString()
});
if (currentFilter) {
params.append('project', currentFilter);
}
const response = await fetch(`${endpoint}?${params}`);
if (!response.ok) {
throw new Error(`Failed to load ${dataType}: ${response.statusText}`);
}
const data = await response.json() as { items: TItem[], hasMore: boolean };
const nextState = {
...stateRef.current,
isLoading: false,
hasMore: data.hasMore
};
stateRef.current = nextState;
setState(prev => ({
...prev,
isLoading: false,
hasMore: data.hasMore
}));
offsetRef.current += UI.PAGINATION_PAGE_SIZE;View on GitHub (pinned to d768ba3643)
Solutions
- Confirm the worker HTTP API is running and reachable from the viewer UI.
- Check the worker logs for the failing endpoint and the returned statusText; fix authentication or project filter values if the request is rejected.
When it happens
Trigger: Fires in the viewer UI when a paginated fetch of sessions/observations/summaries returns a non-2xx response, usually because the worker is not running, the configured worker port is wrong, or the route errored server-side. Guard at src/ui/viewer/hooks/usePagination.ts:55 turns the failed response into a readable error instead of rendering empty data.
Common situations: See trigger scenarios.
AI-assisted analysis of thedotmack/claude-mem@d768ba3643 (2026-08-12).
Data as JSON: /api/errors/3ab49b95a83682fe.
Report an issue: GitHub.