Cancel a session you're bailing on

Three sets in, the wrist twinge becomes a real ache. You're not finishing. The session needs to close cleanly — not as a completed workout, not as a paused one, but as a cancelled session the system can read honestly.

What the agent needs to hear

Behind your sentence, the agent works backwards to two pieces: confirmation that you’re cancelling — not pausing, not ending, cancelling — and, optionally, the reason. The active session is implicit. The reason is optional but useful — injury, time conflict, illness, equipment failure — because it’s what makes the tag readable later.

« Cancel today’s session » is enough. The agent confirms once before applying because cancellation isn’t reversible the way a pause is — once tagged cancelled, you don’t reopen it and keep training; you start a new session if you come back. The single confirmation is the safety net.

Cancel vs pause vs end — the three closing modes

Three modes close a session, and they read very differently downstream. Cancel is for bailing: the session stays in the record tagged « cancelled », and adherence reads it as an incomplete session. Pause is for stepping away with intent to come back — duration freezes, the session stays open, you resume on your terms. End is for finished work: the session closes as completed, every metric counts.

The deciding question is what actually happened. Finished is finished. Paused is « coming back ». Cancelled is « not today ». Don’t « end » a session you bailed on at set 3 — that inflates completion stats. Don’t « pause » indefinitely either — pauses that never resume become orphaned sessions that distort duration trends. Pick the tag that matches reality.

How a cancelled session reads downstream

A cancelled session is not a hidden session. The record stays, the sets you did log stay attached, and three readings include it. Routine adherence counts cancelled days as missed — that’s the point of the tag. Weekly review surfaces the cancellation in the recap with its reason if you gave one. Streak tracking typically breaks the streak on a cancel, unless it falls inside a documented rest pattern.

The honesty of the tag is what makes it useful. The system reads « bailed because of wrist » very differently than a training plateau — one is signal about your body, the other would be a misread of effort. Naming the reason once costs nothing and pays back when a recurring pattern starts to show up.

When the agent gets it wrong

Three failure modes come up. The agent ended the session as completed when you meant cancel — say so plainly: « reopen and cancel it, I didn’t finish ». The agent cancelled the wrong session — yesterday’s accidental open one instead of today’s — name the target: « not that one, cancel today’s, leave yesterday alone ». The agent treated cancel as delete — push back: « keep the record, just tag it cancelled ».

The confirmation card is the chokepoint. Read which session, which tag, which reason — and correct in plain language if any is off.

What makes a clean cancel

Three things decide whether this cancellation reads correctly later: the tag is cancel, not end (ended sessions count toward completion stats; cancelled ones don’t, and the asymmetry only works if the tag is honest), the sets you did log stay attached (a cancelled session with three sets still counts those sets toward volume — losing them would punish you for partial work you actually did), and the reason is captured when it matters (one cancellation is noise; a recurring « wrist » cancellation is a pattern worth flagging). Cancelled sessions, tagged honestly, keep the training story readable across weeks where life or the body said no.