Say what a database or log target's attempt did, without a status (closes #388)

A database or log target sends no HTTP request, yet each of its attempts read "success Status: — (no response)", which for an http target means a failed connection. The shared attempt template now reads a successful database attempt as "archived" and a successful log attempt as "written to the log", and shows no status for either, in the event log and on the event's page. http and slack attempts are unchanged. One test per target type, plus one for a failed database attempt, checks both pages. Model: opus-5-5
2026-10-03 00:33:24 +00:00
parent f1da5e73dd
commit 8514c1e042
3 changed files with 98 additions and 1 deletions
@@ -1899,6 +1899,10 @@ retries) is individually logged for full observability.
 | `error`         | string  | Error message (on failure) |
 | `duration`      | integer | Request duration in milliseconds |

+A `database` or `log` target sends no HTTP request, so in the event log and
+on the event's page its attempts show no status: a successful one reads
+"archived" or "written to the log".
+
 **Relations:** Belongs to Delivery.

 #### EventTotals, TargetTotals and EntrypointTotals