Course contentsShow
← JavaScript
Lesson 1192 of 2,72327. The Event LoopFree lesson

What Goes in the Task Queue

Understand that setTimeout, setInterval, and I/O callbacks are scheduled as tasks.

What Goes in the Task Queue

What you'll learn: You'll discover which specific JavaScript operations end up in the task queue and when they're scheduled.

The Task Queue Population

Now that you know JavaScript has two queues (tasks and microtasks), let's identify what actually populates the task queue. Think of the task queue as the "slow lane" for callbacks that don't need urgent processing.

What Gets Scheduled as Tasks

Three main categories of operations create tasks:

1. setTimeout and setInterval

When you use setTimeout or setInterval, the callback you provide goes into the task queue after the specified delay. These are timer callbacks.

2. I/O Operations

Input/output operations like reading files (in Node.js), network requests, or responding to user events (clicks, key presses) schedule their callbacks as tasks.

3. Other Browser APIs

Operations like requestAnimationFrame, MessageChannel, and similar Web APIs also use the task queue for their callbacks.

Why This Matters

Understanding what goes in the task queue helps you predict when your code will run. Tasks execute one at a time, and only when the call stack is empty. If you have multiple setTimeout calls with the same delay, they'll queue up and execute in order, but each waits for the previous one to complete.

The Simple Rule

If it involves timers or external systems (I/O), its callback becomes a task.

Key Takeaway: setTimeout, setInterval, and I/O callbacks are all scheduled as tasks in the task queue, executing one by one after the call stack clears.