---
title: "Comment by Hayrullah Kar on \"The agent finished its turn. Did the job actually finish?\" | Hashnode"
description: "Counting accepted plus rejected against the input is a useful check, but a count can balance by accident: one row dropped and another written twice still adds u"
url: "https://hashnode.com/posts/the-agent-finished-its-turn-did-the-job-actually-finish/6aeca7659dcf05719b09ac18/comment/6aeec8ac5c8154293b3ac891"
---

[Discussion](https://hashnode.com/posts/the-agent-finished-its-turn-did-the-job-actually-finish/6aeca7659dcf05719b09ac18)

Comment [The agent finished its turn. Did the job actually finish?](https://hashnode.com/posts/the-agent-finished-its-turn-did-the-job-actually-finish/6aeca7659dcf05719b09ac18)

[Hayrullah Kar](https://hashnode.com/@magesheet)

[2d ago](https://hashnode.com/posts/the-agent-finished-its-turn-did-the-job-actually-finish/6aeca7659dcf05719b09ac18/comment/6aeec8ac5c8154293b3ac891)

Counting accepted plus rejected against the input is a useful check, but a count can balance by accident: one row dropped and another written twice still adds up to 12. Checking that every input row ID appears exactly once across the two output files closes that gap, and costs about the same to run.