paperclipai/paperclip · error

Feedback trace upload failed with HTTP

Error message

Feedback trace upload failed with HTTP ${response.status}

What it means

Upload failure in uploadTraceBundle: the POST of the gzipped feedback trace to the endpoint returned a non-2xx status. The HTTP status is embedded (the upstream body text is preferred as detail when available) so the failure can be distinguished from network errors.

Solutions

1. Check network access to the feedback endpoint and retry; inspect the HTTP status in the message for the cause.

When it happens

Trigger: Thrown at server/src/services/feedback-share-client.ts:48 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of paperclipai/paperclip@120ae5428f (2026-08-18). Data as JSON: /api/errors/93c74ba6c21aa569. Report an issue: GitHub.

Appendix: source

Thrown at server/src/services/feedback-share-client.ts:48

        objectKey,
        exportedAt: exportedAt.toISOString(),
        bundle,
      });
      const response = await fetch(endpoint, {
        method: "POST",
        headers: {
          "content-type": "application/json",
          ...(token ? { authorization: `Bearer ${token}` } : {}),
        },
        body: JSON.stringify({
          encoding: "gzip+base64+json",
          payload: gzipSync(requestBody).toString("base64"),
        }),
      });

      if (!response.ok) {
        const detail = await response.text().catch(() => "");
        throw new Error(detail.trim() || `Feedback trace upload failed with HTTP ${response.status}`);
      }

      const payload = await response.json().catch(() => null) as { objectKey?: unknown } | null;
      return {
        objectKey: typeof payload?.objectKey === "string" && payload.objectKey.trim().length > 0
          ? payload.objectKey
          : objectKey,
      };
    },
  };
}

View on GitHub (pinned to 120ae5428f)