Questions
4 of 18
11. What is a thunk in Redux?
22. What is the difference between redux-thunk and createAsyncThunk?
33. How does createAsyncThunk simplify async actions?
44. What are the lifecycle actions automatically created by createAsyncThunk?
55. How do you handle pending, fulfilled, and rejected states in slices?
66. What are the advantages of using createAsyncThunk over manual thunks?
77. How do you pass parameters to a thunk function?
88. How do you handle API errors inside a thunk?
99. How can you cancel a running thunk or API call?
1010. How can you chain multiple async thunks?
1111. How can you use getState and dispatch inside a thunk?
1212. How do you use thunks in combination with RTK Query?
1313. How do you test thunks and async actions?
1414. What are best practices for organizing async logic with thunks?
1515. How do you dispatch a thunk from a React component using hooks?
1616. How do you manage loading indicators with thunks?
1717. What’s the performance implication of using too many thunks?
1818. How can you refactor thunk-based APIs to RTK Query-based APIs?
RTKRTK
Basics
Slice
Actions
Reducers
RTK Query
Store
Thunk
Scenario Based
04 / 18

4. What are the lifecycle actions automatically created by createAsyncThunk?

Lifecycle Actions in createAsyncThunk

When you create an async thunk using createAsyncThunk in Redux Toolkit, it automatically generates three distinct action types that represent the lifecycle of an asynchronous operation — pending, fulfilled, and rejected.

Lifecycle Actions Created Automatically
  1. 1

    1. pending: Dispatched when the async function is first called. Typically used to set a loading state or show a spinner in the UI.

  2. 2

    2. fulfilled: Dispatched when the async operation completes successfully. The returned data becomes the action’s payload.

  3. 3

    3. rejected: Dispatched when the async operation fails due to an error, timeout, or rejection. Contains the error message for debugging or display.

Example: Handling Lifecycle Actions in a Slice

These lifecycle actions allow developers to handle loading, success, and error states in a predictable and structured way, reducing boilerplate and improving async flow management.