Writing fails halfway through
The tag may now hold something between the old content and the new. Read it before rewriting, because what you find decides whether this was a slipped hand or a tag that cannot hold a write. Rewriting immediately destroys that evidence.
What state the tag is in
A write is not a single instant. Content is transferred and committed in pieces, so an interruption can leave the tag holding part of the new message.
Three outcomes are possible. The tag still holds the old content, because nothing was committed. It holds the new content, because the interruption came after the last commit. Or it holds something incoherent that is neither.
The third is the one that matters, because a tag in that state can read as empty, as corrupt, or as a message that stops partway.
Read before rewriting
The instinct is to write again immediately. Doing so destroys the only evidence you have about what happened.
Read the tag first and note what it holds. Old content means nothing was committed and the tag is fine. New content means the write actually completed. Incoherent content means the interruption landed mid commit.
That distinction tells you whether this was a slipped hand or a tag with a problem, and those lead to different responses.
It takes seconds and it is the difference between diagnosing and guessing.
Why it stopped
The phone moved. A write takes longer than a read, and a gesture adequate for reading is regularly too brief for writing. This is the cause in most cases.
The coupling was marginal. A thick case, a small tag, or an awkward surface leaves too little margin for the longer exchange.
The tag is failing. A fatigued bond between chip and antenna can hold a connection long enough to start a write and not long enough to finish it.
Something interrupted the phone: a call, a notification taking focus, the screen locking. Less common and worth ruling out if the pattern fits.
Resuming safely
Rest the phone on the tag rather than holding it, and do not move until the application confirms.
Remove the case for the write, since the margin matters more here than for reading.
Rewrite the whole message rather than trying to continue. There is no resume, and a write replaces the message rather than appending to it.
Then read it back and confirm. A tag that failed once and succeeded on the second attempt is fine. A tag that fails halfway repeatedly, in a position where a fresh tag succeeds, is damaged and should be replaced.
Frequently asked questions
Is the tag damaged after a failed write?
Usually not. An interrupted write leaves the memory in whatever state it reached, and a complete rewrite normally restores it.
Can I resume where it stopped?
No. A write replaces the whole message, so the only option is to write it again from the start.
Why does writing take longer than reading?
Because the tag has to commit the data rather than just recite it. That is why a gesture that reads reliably can be too brief to write.
Should I erase before rewriting?
Not normally, since a write replaces the message. Erasing first is worth it when a tag reads as incoherent and you want a clean starting state.