Finally block in Javascript - Step-by-Step Execution

Concept Flow - Finally block

Start try block

↓

Execute try code

↓

Error?

Yes→Catch block runs

↓

Execute catch code

↓

Try block ends

↓

Finally block runs

↓

End

The finally block runs after try and catch blocks, no matter if an error happened or not.

Execution Sample

Javascript

try {
  console.log('Try block');
  throw new Error('Oops');
} catch (e) {
  console.log('Catch block');
} finally {
  console.log('Finally block');
}

This code runs try, then catch because of error, then finally always.

Execution Table

Step	Action	Output	Next Step
1	Enter try block	No output yet	Execute console.log('Try block')
2	console.log('Try block')	Try block	Throw error new Error('Oops')
3	throw new Error('Oops')	Error thrown	Jump to catch block
4	Enter catch block	No output yet	Execute console.log('Catch block')
5	console.log('Catch block')	Catch block	Enter finally block
6	Enter finally block	No output yet	Execute console.log('Finally block')
7	console.log('Finally block')	Finally block	End execution

💡 Finally block runs last regardless of error; execution ends after finally.

Variable Tracker

Variable	Start	After Step 3	After Step 7
Error thrown	No	Yes (Error object)	Handled (catch)

Key Moments - 3 Insights

Does the finally block run if there is no error in the try block?

Yes, the finally block always runs after try, even if no error occurs, as shown by the flow from try to finally in the execution_table.

If an error is thrown in the try block, does the finally block still run?

Yes, even if an error occurs and catch runs, the finally block runs afterward, as seen in steps 3 to 7 in the execution_table.

Can the finally block change the error handling flow?

The finally block runs last and cannot prevent catch from running, but if it throws an error itself, it can affect the flow (not shown here).

Visual Quiz - 3 Questions

Look at the execution_table, what is printed at step 2?

A Finally block

B Catch block

C Try block

D No output

💡 Hint

Check the Output column for step 2 in the execution_table.

At which step does the catch block start running?

A Step 4

B Step 2

C Step 3

D Step 6

💡 Hint

Look at the Action column to find when catch block is entered.

If the throw statement in try is removed, which step would no longer happen?

A Step 5 (console.log in catch)

B Step 3 (throw error)

C Step 6 (enter finally)

D Step 2 (console.log in try)

💡 Hint

Refer to the execution_table rows where error is thrown and catch runs.

Concept Snapshot

try {
  // code that may throw
} catch (error) {
  // handle error
} finally {
  // always runs
}

- finally runs no matter what
- runs after try and catch
- useful for cleanup

Full Transcript

The finally block in JavaScript runs after the try and catch blocks no matter what happens. If the try block runs without errors, finally still runs. If an error occurs, catch runs, then finally runs. This ensures code in finally always executes, useful for cleanup tasks. The execution steps show try running, error thrown, catch handling error, then finally running last.

Practice

1.

What is the main purpose of the finally block in JavaScript?

easy

A. To define variables used in try block

B. To run code that always executes after try and catch blocks

C. To catch errors thrown in the try block

D. To skip the catch block if no error occurs

Solution

1. Step 1: Understand try-catch-finally structure

   The try block runs code that might throw errors, catch handles those errors.

2. Step 2: Role of finally block

   The finally block runs code after try and catch, no matter if an error occurred or not.

3. Final Answer:

   To run code that always executes after try and catch blocks -> Option B

4. Quick Check:

   finally always runs = C [OK]

Hint: finally always runs after try/catch, no matter what [OK]

Common Mistakes:

• Thinking finally only runs if there is an error
• Confusing catch and finally blocks
• Believing finally can catch errors

2.

Which of the following is the correct syntax to add a finally block after a try and catch block?

try {
  // code
} catch (e) {
  // handle error
} ??? {
  // cleanup code
}

easy

A. cleanup

B. final

C. finally

D. end

Solution

1. Step 1: Recall JavaScript error handling syntax

   The correct keyword after catch is 'finally' to run code always.

2. Step 2: Check options for correct keyword

   Only 'finally' is valid JavaScript syntax here.

3. Final Answer:

   finally -> Option C

4. Quick Check:

   finally keyword syntax = D [OK]

Hint: finally is the exact keyword after catch for cleanup [OK]

Common Mistakes:

• Using 'final' or 'end' instead of 'finally'
• Omitting the finally block keyword
• Placing finally before catch

3.

What will be the output of this code?

function test() {
  try {
    console.log('Try block');
    return 'Return from try';
  } catch (e) {
    console.log('Catch block');
  } finally {
    console.log('Finally block');
  }
}
console.log(test());

medium

A. Finally block\nReturn from try

B. Try block\nCatch block\nFinally block\nReturn from try

C. Try block\nReturn from try

D. Try block\nFinally block\nReturn from try

Solution

1. Step 1: Trace the try block execution

   It logs 'Try block' and then hits return 'Return from try'.

2. Step 2: Understand finally runs after return

   Even after return, finally runs and logs 'Finally block'. Then function returns.

3. Final Answer:

   Try block\nFinally block\nReturn from try -> Option D

4. Quick Check:

   finally runs after return = A [OK]

Hint: finally runs even after return in try [OK]

Common Mistakes:

• Thinking finally does not run after return
• Expecting catch block to run without error
• Missing the order of console logs

4.

Find the error in this code snippet:

try {
  throw new Error('Oops');
} catch {
  console.log('Caught error');
} finally {
  console.log('Cleanup');
}

medium

A. No error, code runs fine

B. finally block cannot be used without catch parameter

C. throw statement is incorrect

D. Missing error parameter in catch block

Solution

1. Step 1: Check catch block syntax

   Optional catch binding (ES2019+) allows catch {} without parameter. Valid in modern JavaScript.

2. Step 2: Verify execution

   Throws error, catch logs 'Caught error', finally logs 'Cleanup'. No errors.

3. Final Answer:

   No error, code runs fine -> Option A

4. Quick Check:

   catch {} valid = D [OK]

Hint: catch {} valid in modern JS with optional binding [OK]

Common Mistakes:

• Thinking catch always requires parameter
• Believing syntax error without catch param
• Confusing with pre-ES2019 JS

5.

Consider this code:

let result = '';
function test() {
  try {
    result += 'Try';
    throw new Error('Error!');
  } catch (e) {
    result += 'Catch';
    return result;
  } finally {
    result += 'Finally';
  }
}
test();
console.log(result);

What will be printed to the console?

hard

A. TryCatchFinally

B. TryCatch

C. TryFinally

D. Try

Solution

1. Step 1: Trace try block execution

   result becomes 'Try', then error is thrown.

2. Step 2: Catch block runs and appends 'Catch', then returns result ('TryCatch')

   Before returning, finally runs and appends 'Finally' to result.

3. Step 3: Check console.log output

   console.log prints result after finally appended, so 'TryCatchFinally'.

4. Final Answer:

   TryCatchFinally -> Option A

5. Quick Check:

   finally runs before return completes = B [OK]

Hint: finally runs before return completes, modifies variables [OK]

Common Mistakes:

• Assuming return stops finally from running
• Expecting console.log to print before finally modifies result
• Ignoring that finally runs even after return