OUT-3598: surface Dropbox 409 reasons in Sentry titles

[SandipBajracharya]

Summary

• Closes the last-mile gap on DROPBOX-INTEGRATION-17: DropboxClient.buildDropboxResponseError now embeds Dropbox's error_summary into the constructed DropboxResponseError's runtime .message, so Sentry titles read e.g. Response failed with a 409 code: path/not_found/.. instead of opaque Response failed with a 409 code.
• Trigger.dev retry behavior is intentionally unchanged — per the ticket, we want to see real error_summary data from the next occurrence before deciding on any per-reason handling.

Why

Earlier OUT-3598 commits (0426a12, dcce588) already parse Dropbox's response body and put the error_summary on the error payload — but Sentry uses Error.message for issue titles, so the parsed reason was invisible there. This final commit mutates .message post-construction so the reason rides through to Sentry's title.

Test plan

• After deploy, wait for the next DROPBOX-INTEGRATION-17 event in Sentry and confirm the title now contains the Dropbox reason (e.g. path/not_found/..).
• If the title is still opaque, the failure path is going through an SDK call rather than the manual-fetch content endpoint — file a separate ticket for that instrumentation gap.

Out of scope (tracked separately)

• src/utils/withErrorHandler.ts:51-54 has a mirror branch-ordering bug (instanceof Error shadows instanceof DropboxResponseError) that affects API route responses — not the Sentry path. To be addressed in its own ticket.
• Per-reason handling (skip on path/not_found, mark-failed on restricted_content, etc.) — explicitly deferred until real data lands.

Linear: https://linear.app/assemblycom/issue/OUT-3598/dropboxresponseerror-response-failed-with-a-409-code

🤖 Generated with Claude Code

[linear-code]

OUT-3598

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dropbox-integration	Ready	Preview, Comment	May 11, 2026 0:02am

[greptile-apps]

Greptile Summary

This PR closes the last-mile observability gap for Dropbox content-endpoint errors by embedding Dropbox's error_summary string into DropboxResponseError.message inside buildDropboxResponseError, so Sentry issue titles show the specific failure reason (e.g. path/not_found/..) rather than an opaque status-code string.

• buildDropboxResponseError now reads error_summary from the constructed errorPayload and appends it to the error's .message via a cast to Error, leaving retry behavior and the error payload shape unchanged.
• The fallback path (rawBody || fallbackSummary) already existed for non-JSON responses; this PR now also embeds that value into .message, which could produce very long titles if the body is an HTML error page from a proxy or gateway.

Confidence Score: 4/5

Safe to merge for the targeted 409 Sentry-title improvement; the only rough edge is in the non-JSON fallback path, which is unlikely to fire for the 409 case this PR is fixing.

The change is tightly scoped: one method, one new assignment to .message. For 409 responses Dropbox always returns JSON with error_summary, so the happy path works exactly as intended. The fallback path — which sets error_summary to the raw response body for non-JSON errors — could embed a large blob into the Sentry title, but this scenario (proxy/gateway HTML errors) is uncommon in the Dropbox content-endpoint context and doesn't cause data loss or incorrect retry behavior.

src/lib/dropbox/DropboxClient.ts — specifically the fallback branch in buildDropboxResponseError where rawBody becomes the embedded summary for non-JSON error responses.

Important Files Changed

Filename	Overview
src/lib/dropbox/DropboxClient.ts	Adds error_summary embedding into DropboxResponseError.message in buildDropboxResponseError; the fallback path can embed an unbounded raw response body into the message when the Dropbox API returns a non-JSON error.

Sequence Diagram

sequenceDiagram
    participant Caller as _downloadFile / _uploadFile
    participant BDRB as buildDropboxResponseError
    participant DBX as Dropbox API
    participant Sentry

    Caller->>DBX: manualFetch(url, headers)
    DBX-->>Caller: response (non-200)
    Caller->>BDRB: buildDropboxResponseError(response, fallbackSummary)
    BDRB->>DBX: response.text()
    DBX-->>BDRB: rawBody
    Note over BDRB: Parse JSON → errorPayload
    BDRB->>BDRB: new DropboxResponseError(status, headers, errorPayload)
    BDRB->>BDRB: Extract error_summary string
    BDRB->>BDRB: "(err as Error).message = message + summary"
    BDRB-->>Caller: DropboxResponseError (enriched .message)
    Caller-->>Sentry: "throw err → Sentry title = err.message"

Loading

_{Reviews (1): Last reviewed commit: "fix(OUT-3598): embed Dropbox error_summa..." | Re-trigger Greptile}