Skip to main content

​
Ask, in whatever conversation you are in

Tell your assistant to cancel the task — by id, or by describing it if there is only one in flight. Your assistant calls Hence Assistant, and the task stops. You can also simply decline. Any question Hence Assistant asks can be answered no, and an errand that cannot proceed without an answer ends rather than working around you.

​
What cancelling guarantees

Cancellation is cooperative: the errand is told to stop and stops where it can do so safely, rather than being killed mid-step. That is what keeps a half-submitted form from existing. What it guarantees:
  • Nothing you would have been asked about proceeds. Every act on your behalf — a message sent, a setting changed, a form submitted — pauses for your answer first, and the errand reads the cancellation when it wakes from that pause. It ends there instead of acting.
  • The task ends in cancelled, a terminal state of its own, carrying what had been done up to that point and what had not. It is deliberately not reported as DONE or READY: neither would be true of an errand you stopped.
  • Receipts for what already happened stay. They are the record of acts that did occur.
What it does not guarantee, and this is a real gap rather than a nicety: a step already under way is not interrupted. It runs to its own end — five minutes at the outside — before the stop is seen, and a step that needs no answer from you, such as reading a rate off a page, can still run until the errand next pauses. What cannot happen in that window is an act you were never asked about.

​
What it does not do

Cancelling stops future acts. It does not reverse acts already taken — that is what the reversibility limits are for, rather than something cancellation could offer. If a deferral rate was already changed on your approval, cancelling the task does not change it back; changing it back is its own errand, and it is one step in the same portal. This is also why errands that do irreversible things are not in the current set. The 401(k) rollover stops at the review page precisely so that “stop” is always a real option.

​
Disconnecting your assistant

Removing the connector in your host stops it calling Hence Assistant at all. That is the blunt instrument, and it works immediately.
Removing the connector does not stop an errand already running, and does not purge your data. Hence Assistant can now cancel every live errand of yours the moment a connection is revoked — that half is built, and it is the same cooperative stop described above — but nothing signals the revocation yet: your host does not tell us the connector is gone, and there is no disconnect action in the Hence app. Until one exists, cancel a task explicitly before you disconnect, and see Trust and control for how to ask for erasure.