paperclipai/paperclip · error
Failed to request restart (${res.status})
Error message
Failed to request restart (${res.status}) What it means
The UI's POST to /api/health/dev-server/restart returned a non-OK status. Same pattern as health get: server error payload if present, otherwise this status-bearing fallback message surfaced to the operator.
Source
Thrown at ui/src/api/health.ts:66
const res = await fetch("/api/health", {
credentials: "include",
headers: { Accept: "application/json" },
});
if (!res.ok) {
const payload = await res.json().catch(() => null) as { error?: string } | null;
throw new Error(payload?.error ?? `Failed to load health (${res.status})`);
}
return res.json();
},
requestDevServerRestart: async (): Promise<void> => {
const res = await fetch("/api/health/dev-server/restart", {
method: "POST",
credentials: "include",
headers: { Accept: "application/json" },
});
if (!res.ok) {
const payload = await res.json().catch(() => null) as { error?: string } | null;
throw new Error(payload?.error ?? `Failed to request restart (${res.status})`);
}
},
};
View on GitHub (pinned to a7e689b3c3)
Solutions
- Verify the server is running and you have permission to request a restart, then retry.
- Re-authenticate if the status is 401/403.
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at ui/src/api/health.ts:61 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of paperclipai/paperclip@a7e689b3c3 (2026-08-18).
Data as JSON: /api/errors/bfcba874faf60e61.
Report an issue: GitHub.