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

In the event log and on an event's page, every attempt by a `database` or `log` target read "success Status: — (no response)". Those targets make no HTTP request, so there is no response to have, and "no response" reads like a failed connection, which is what it means for an `http` target. A successful `database` attempt now reads "archived" and a successful `log` attempt "written to the log", with no status shown; a failed one keeps "failure" and its error line, also with no status. `http` and `slack` attempts are unchanged. The change is in the one shared attempt template. Model: opus-5-5
2026-10-03 02:41:17 +02:00
parent f1da5e73dd
commit bcdd4791ec
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