---
title: "Comment by Mike Dabydeen on \"Silent Failures: What to Log When a Bug Leaves No Error\" | Hashnode"
description: "I'd split the funnel record into a start and an end, because emitting it after the run leaves the accounting rule with nothing to check in the case that hurts m"
url: "https://hashnode.com/posts/what-to-log-silent-failures-decision-records/6afa862cc1fd081482ee4d9b/comment/6afaf56e1694eeaed3bd0bf3"
---

[Discussion](https://hashnode.com/posts/what-to-log-silent-failures-decision-records/6afa862cc1fd081482ee4d9b)

Comment [Silent Failures: What to Log When a Bug Leaves No Error](https://hashnode.com/posts/what-to-log-silent-failures-decision-records/6afa862cc1fd081482ee4d9b)

[Mike Dabydeen](https://hashnode.com/@firelinks)

[6d ago](https://hashnode.com/posts/what-to-log-silent-failures-decision-records/6afa862cc1fd081482ee4d9b/comment/6afaf56e1694eeaed3bd0bf3)

I'd split the funnel record into a start and an end, because emitting it after the run leaves the accounting rule with nothing to check in the case that hurts most. When a worker hits its memory limit, the kernel kills it with SIGKILL, and Python never runs the finally block. The item in flight and the run record both vanish, so the run looks the same as one that never started.

If digest.run.start goes out as soon as the query returns, carrying run\_id and selected, an end record can close it. A start with no end after the job's normal duration means it died partway, and selected minus the decision records already written tells you how many users it left behind. A missing start at the scheduled time catches the cron that never fired, which is the never-reached case from your third bullet.
