{
  "id": 17707342,
  "title": "Do not implement cancellation request processing as history deletion: a small design that separates suspension and compensation confirmation.",
  "url": "https://urgent.news/2026/11/02/story-17707342",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-02T00:09:33.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/officialmailkr/cwiso-yoceongeul-ceori-iryeog-sagjero-guhyeonhaji-anhgi-jungdangwa-bosang-hwagineul-nanuneun-jageun-seolgye-3b9p"
  },
  "original_language": "ko",
  "account": "This article discusses the concept design for a small business tool that handles request cancellations. It highlights the importance of distinguishing between a requester's cancellation intention and the actual execution result. The article proposes a system that tracks request status and execution status separately, with the former including \"valid\" and \"withdrawn\" states, and the latter including \"waiting\", \"in progress\", \"interrupted\", and \"completed\" states. The system also considers follow-up actions, such as confirming or taking measures, and notes that cancellation notifications should be handled carefully to avoid duplicate actions or incorrect status updates.",
  "summary": "A customer has sent an email saying, \"Please cancel this request.\" If the request is still in the queue, it can be stopped by blocking it, but if the request has already been sent externally, the same action cannot be taken. However, if all cases are covered with a single \"cancelled\" value, it becomes difficult to explain what was stopped and what remains. This article is a conceptual design for a small business tool. It does not mean that the following functions are implemented in official emails. The intention to cancel and the execution result are on different axes. The requester's intention may change to \"withdrawn,\" but the \"completed\" execution history does not automatically disappear. It is easier to understand if the following facts are stored separately rather than adding another status. Request status: valid / withdrawn Execution status: waiting / in_progress / paused / confirmed / completed ...",
  "key_points": [
    "Cancel requests can be halted if still in queue, but not if already completed.",
    "Separate cancellation intentions from execution results for clear explanation.",
    "Maintain distinct follow-up verification status for accurate progress tracking."
  ],
  "editors_take": "Separating cancellation intentions from execution results prevents data loss and ensures that irreversible external actions remain verifiable even when a user attempts to withdraw a request.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}