Delivery failures are invisible in the UI: nothing renders status_code, response_body, error or attempt_num #202

New Issue

clawbot · 2026-08-20T05:47:14+02:00

clawbot commented

2026-08-20 05:47:14 +02:00

delivery_results stores status_code, response_body, error, duration and attempt_num, and no template renders any of it. A grep of templates/ finds no StatusCode, ResponseBody or Attempt. The event log renders only {{.Target.Name}}: {{.Status}} (templates/source_logs.html:26-30), so a failure reads echo-sink: failed and nothing else.

Diagnosing why a delivery failed currently requires opening the per-webhook SQLite file by hand. For a store-and-forward proxy that is the first question an operator asks, so this is a 1.0 gap rather than a polish item.

Related but distinct: #107 covers terminal-state correctness in the engine. This issue is purely the read path.

Definition of done:

expanding a delivery on the source detail / event log page shows, per attempt: attempt number, status code, duration, the error string, and the response body
the response body is bounded in the query the same way event bodies are (see #135), not read whole and truncated in Go
target config and any credential-bearing field stay masked, consistent with #113, #115 and Slack webhook credential still leaks via delivery errors, SSRF logs, and the source_logs template data (#118)
a handler test asserts a failed delivery's status code and error reach the rendered page

`delivery_results` stores `status_code`, `response_body`, `error`, `duration` and `attempt_num`, and no template renders any of it. A grep of `templates/` finds no `StatusCode`, `ResponseBody` or `Attempt`. The event log renders only `{{.Target.Name}}: {{.Status}}` (`templates/source_logs.html:26-30`), so a failure reads `echo-sink: failed` and nothing else. Diagnosing why a delivery failed currently requires opening the per-webhook SQLite file by hand. For a store-and-forward proxy that is the first question an operator asks, so this is a 1.0 gap rather than a polish item. Related but distinct: #107 covers terminal-state correctness in the engine. This issue is purely the read path. Definition of done: - expanding a delivery on the source detail / event log page shows, per attempt: attempt number, status code, duration, the error string, and the response body - the response body is bounded in the query the same way event bodies are (see #135), not read whole and truncated in Go - target config and any credential-bearing field stay masked, consistent with #113, #115 and #118 - a handler test asserts a failed delivery's status code and error reach the rendered page

clawbot added this to the 1.0.0 milestone 2026-08-20 05:47:14 +02:00

clawbot referenced this issue

2026-08-20 05:49:42 +02:00

1.0/mvp #33

clawbot referenced this issue

2026-08-20 05:56:52 +02:00

Milestone 1.0.0: internet-facing readiness #111

clawbot referenced this issue from a commit

2026-08-20 06:21:31 +02:00

Render delivery attempt detail in the event log (closes #202)

clawbot referenced a pull request that will close this issue

2026-08-20 06:22:02 +02:00