PR Custody

feat(logs): fetch decrypted log details from Apollo instead of raw ClickHouse

@sarahsimionescuchecks n/achecks…feat/decrypted-log-details → main2 files · +134 −105review: @shamsharoonupdated 2d ago

▸Description· 1 comment · 2 noise

Summary

Refs SUP-449, SUP-451.

The log-detail panel showed encrypted iv:cipher:tag blobs (payload sections were commented out entirely) because getLogDetail selected encrypted payload columns straight from ClickHouse. Apollo decrypts on read behind project-scoped authZ, so:

Trigger detail now calls GET /api/v3.1/internal/trigger/log/{id} — decrypted provider payload, client payload/response, plus new fields: webhook request id (webhookEventId), triggerConfig, triggerType, processingError, delivery statuses.
Tool (action) detail keeps its ClickHouse row but overlays decrypted request/response/errorRequest from GET /api/v3.1/internal/action_execution/log/{id} (non-fatal — falls back to row values if Apollo is unreachable).
Trigger detail panel: re-enabled the previously commented-out payload sections (provider payload, payload sent + Resend button, response/error), added a Request ID row and a Processing Error section.

Deploy ordering

⚠️ Depends on backend PR https://github.com/ComposioHQ/platform/pull/10644 — the new meta fields only exist there. Until it deploys, the code degrades gracefully (zod-optional fields; Request ID / Processing Error simply don't render), but trigger status won't reflect processing-only errors. Merge/deploy the Apollo PR first.

Notes

Payloads are shown as stored (no key scrubbing) — same as the pre-encryption behavior; sensitive-value scrubbing is deferred pending a team decision.
List queries (getTriggerLogs, action lists) intentionally still hit ClickHouse directly — they don't select payload columns and stay fast.
Very old logs without a connection nanoId will show "N/A" for connected account instead of the raw UUID (Apollo's meta only carries the nanoId).

Test plan

tsgo --noEmit: 0 errors. oxlint: 0 errors (warnings = pre-existing baseline).
Manual: trigger + action log detail panels against a local/staging Apollo with the backend branch.

🤖 Generated with Claude Code

@sarahsimionescu2d ago

Backend counterpart: https://github.com/ComposioHQ/platform/pull/10644 (must deploy first).

▸ 2 bot/status comments hidden

@linear-code[bot]2d ago

Tool execution logs section on dashboard doesn't show the request and response of the tool call

Screenshot 2026-06-03 at 8.29.20 PM.png

Logs filtering has some issues, please check the slack thread here

The trigger logs currently shown on the dashboard are encrypted - we need to fix this by decrypting them before displaying

CleanShot 2026-06-03 at 00.27.38@2x.png

@vercel[bot]2d ago

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

Project	Deployment	Actions	Updated (UTC)
dashboard	Ready

loading diff…