CancellationException behavior in Kotlin - Step-by-Step Execution

Concept Flow - CancellationException behavior

Start Coroutine

↓

Check for Cancellation?

No→Continue Execution

Yes↓

Throw CancellationException

↓

Coroutine Cancelled

↓

Catch CancellationException?

Yes→Handle Cancellation

No↓

Propagate Exception

This flow shows how a coroutine checks for cancellation, throws CancellationException, and how it can be caught or propagated.

Execution Sample

Kotlin

import kotlinx.coroutines.*

fun main() = runBlocking {
  val job = launch(Dispatchers.Default) {
    delay(100)
    println("Still running")
  }
  job.cancel()
  job.join()
  println("Done")
}

This code launches a coroutine, cancels it before delay ends, and waits for completion.

Execution Table

Step	Action	Coroutine State	Exception Thrown	Output
1	Launch coroutine	Active	None
2	Start delay(100)	Active	None
3	Call job.cancel()	Cancelling	None
4	Coroutine checks cancellation during delay	Cancelling	CancellationException
5	Coroutine stops due to CancellationException	Cancelled	CancellationException
6	job.join() waits for coroutine completion	Cancelled	None
7	Print "Done"	Cancelled	None	Done

💡 Coroutine cancelled by CancellationException during delay, then job.join() completes and main prints "Done".

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	Final
job.isActive	false	true	false	false	false
job.isCancelled	false	false	true	true	true
job.isCompleted	false	false	false	true	true

Key Moments - 2 Insights

Why does the coroutine stop even though no explicit exception handling is shown?

Because CancellationException is special in coroutines: it is thrown internally to stop the coroutine when cancelled, and it is not treated as a failure unless caught. See execution_table rows 4 and 5.

What happens if we do not call job.join() after cancelling?

Without job.join(), the main coroutine might finish before the launched coroutine fully cancels, causing unpredictable output timing. The join ensures the coroutine completes cancellation before continuing. See execution_table row 6.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what exception is thrown inside the coroutine?

A NullPointerException

B IllegalStateException

C CancellationException

D No exception

💡 Hint

Check the 'Exception Thrown' column at step 4 in the execution_table.

At which step does the coroutine state become 'Cancelled'?

A Step 4

B Step 5

C Step 3

D Step 7

💡 Hint

Look at the 'Coroutine State' column in the execution_table to find when it changes to 'Cancelled'.

If we remove job.join(), what is the likely effect on the output?

A "Done" might print before coroutine cancellation completes

B "Still running" will always print

C Program will crash with exception

D No change in output

💡 Hint

Refer to key_moments explanation about job.join() ensuring coroutine completion.

Concept Snapshot

CancellationException in Kotlin coroutines:
- Thrown internally when coroutine is cancelled
- Stops coroutine execution without failure
- Can be caught to handle cancellation
- Use job.cancel() to request cancellation
- Use job.join() to wait for coroutine to finish cancelling

Full Transcript

This visual trace shows how Kotlin coroutines handle cancellation using CancellationException. When a coroutine is cancelled, it throws CancellationException internally to stop execution. This exception is special and does not count as a failure unless caught. The example code launches a coroutine that delays for 100ms, but it is cancelled before delay ends. The coroutine throws CancellationException and stops. The main coroutine waits for cancellation to complete using job.join() before printing "Done". Variables track the coroutine state changes from active to cancelling to cancelled. Key moments clarify why the coroutine stops without explicit exception handling and why join() is important. The quiz tests understanding of when exceptions occur, state changes, and effects of removing join().