Callback pitfalls in Javascript - Step-by-Step Execution

Concept Flow - Callback pitfalls

Start function with callback

↓

Call async operation

↓

Async operation finishes

↓

Invoke callback

↓

Callback runs with data

↓

Possible issues: callback called multiple times or not at all

↓

End

This flow shows how a callback is passed to an async function, then called later, highlighting common pitfalls like multiple calls or missing calls.

Execution Sample

Javascript

function fetchData(callback) {
  setTimeout(() => {
    callback('data1');
    callback('data2');
  }, 1000);
}

fetchData(console.log);

This code calls the callback twice after 1 second, which can cause unexpected behavior.

Execution Table

Step	Action	Callback Called?	Callback Argument	Effect
1	fetchData called with console.log	No	N/A	Waiting 1 second
2	Timeout triggers first callback call	Yes	'data1'	Logs 'data1'
3	Timeout triggers second callback call	Yes	'data2'	Logs 'data2'
4	No more callback calls	No	N/A	Execution ends

💡 Callback called twice, which can cause unexpected repeated actions.

Variable Tracker

Variable	Start	After 1	After 2	Final
callback calls count	0	1	2	2

Key Moments - 2 Insights

Why is calling the callback twice a problem?

Because the callback runs code that expects to be called once, multiple calls can cause repeated side effects or errors, as shown in execution_table steps 2 and 3.

What happens if the callback is never called?

The caller waits forever for a response, causing the program to hang or timeout, which is a common pitfall if async code forgets to call the callback.

Visual Quiz - 3 Questions

Look at the execution table, how many times is the callback called?

A Twice

B Once

C Never

D Three times

💡 Hint

Check the 'Callback Called?' column in the execution_table rows 2 and 3.

At which step does the callback first get called?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Callback Called?' column and find the first 'Yes'.

If the callback was called only once, how would 'callback calls count' change in variable_tracker?

A It would stay 0

B It would be 2 after first call

C It would be 1 after first call and final

D It would be 3 after final

💡 Hint

Check variable_tracker row for 'callback calls count' and imagine only one callback call.

Concept Snapshot

Callbacks are functions passed to async code to run later.
Pitfall: calling callback multiple times causes repeated effects.
Pitfall: not calling callback causes hanging.
Always ensure callback is called exactly once.
Use flags or promises to avoid multiple calls.

Full Transcript

This example shows a function fetchData that takes a callback and calls it twice after a delay. The execution table traces each callback call and its effect. The variable tracker counts how many times the callback runs. Key moments explain why multiple calls cause problems and what happens if callback is never called. The quiz tests understanding of callback call counts and timing. Remember, callbacks should be called once to avoid bugs.