---
title: "Comment by Arnold Holm on \"The Permanent Halt That Lasts Until the Next Restart\" | Hashnode"
description: "Saving the breach flag and day-start value together fixes the restart problem you describe. I would also test a restart during the file write: if the saved stat"
url: "https://hashnode.com/posts/the-permanent-halt-that-lasts-until-the-next-restart/6ab822dcd23af1cc3fb16f4e/comment/6ac8e97828d22e2e60bf0a2f"
---

[Discussion](https://hashnode.com/posts/the-permanent-halt-that-lasts-until-the-next-restart/6ab822dcd23af1cc3fb16f4e)

Comment [The Permanent Halt That Lasts Until the Next Restart](https://hashnode.com/posts/the-permanent-halt-that-lasts-until-the-next-restart/6ab822dcd23af1cc3fb16f4e)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 9](https://hashnode.com/posts/the-permanent-halt-that-lasts-until-the-next-restart/6ab822dcd23af1cc3fb16f4e/comment/6ac8e97828d22e2e60bf0a2f)

Saving the breach flag and day-start value together fixes the restart problem you describe. I would also test a restart during the file write: if the saved state is missing or unreadable, new entries should stay disabled until it is restored, rather than use the current equity as a fresh baseline. Does the revised version keep the halt in that interrupted-write case?