What Should a Cancel Button Promise?

Question

You start a long-running export, then press Cancel. The button disappears, but the server may already be working. What should the interface promise at that moment?

I would distinguish three outcomes: cancellation requested, stopped before completion, and completed before the request could take effect. Calling all three “cancelled” could leave someone unsure whether a file still exists or whether they should retry.

There is also a difference between closing a progress window and stopping the underlying job. If closing the window only hides it, I would label that action “Close” or “Run in background” rather than “Cancel”.

For work with partial results, the final message should explain what remains. A stop request should not silently imply that earlier changes were rolled back.

When should Cancel become unavailable, and what would you show while the server is still confirming the outcome? Would you keep a visible job record after the dialog closes?

Cover: original AI-generated concept illustration of a parcel conveyor and stop button, not a real product interface.