Redux Toolkit warns that a non-serializable value is in an action or state
A non-serializable value was detected in an action, in the path: `payload.dueDate`Short answer
Redux Toolkit logs this warning in development when an action or the state holds something that is not plain data: a Date, class instance, Map, Set, function or Promise. Read the path in the message, convert the value (for example with toISOString), or ignore that one path or action type.
Fix it fast
1Find out which cause you have
Read the path in the console message. It names the exact field that holds the bad value, and the value printed after it tells you its type.
// Browser console: the warning ends with the path and the value, e.g. payload.dueDate2Match what you see, then jump to its fix
- 1
The path points at a field you build yourself, such as payload.dueDateA Date, class instance, Map, Set, function or Promise went into an action or stateFix - 2
The same path warns on every dispatch and you accept the trade-offOne known path or action type must carry a non-serializable valueFix - 3
Warnings mention action types such as persist/PERSIST or persist/REHYDRATEredux-persist dispatches its own actionsFix
- 1
What does the error look like?
A non-serializable value was detected in an action, in the path: `payload.dueDate`A non-serializable value was detected in the state
Cause 1 of 3
A Date, class instance, Map, Set, function or Promise went into an action or state
1Check
By default the check accepts undefined, null, strings, booleans, numbers, arrays and plain objects; Dates, Maps and other class instances fail.
grep -rn "new Date\|new Map\|new Set" src/features/2Fix
Convert before dispatching: store dueDate.toISOString() instead of a Date, a plain object instead of a class instance, and keep functions and Promises out of actions.
dispatch(taskAdded({ title, dueDate: dueDate.toISOString() }));
// rebuild the Date where you display it: new Date(task.dueDate)3Verify
Dispatch the action again and watch the console stay quiet.
npm run devConfirmed by redux.js.org
Cause 2 of 3
One known path or action type must carry a non-serializable value
1Check
The docs say this should be rare, and such payloads should not reach state through a reducer. If it is truly needed, limit the exception.
grep -rn "serializableCheck" src/2Fix
Ignore the specific action type or path instead of disabling the check.
const store = configureStore({
reducer,
middleware: (getDefaultMiddleware) =>
getDefaultMiddleware({
serializableCheck: {
ignoredActions: ['your/action/type'],
ignoredActionPaths: ['meta.arg', 'payload.timestamp'],
ignoredPaths: ['items.dates'],
},
}),
});3Verify
The warning for that path is gone and warnings for other fields still appear.
npm run devConfirmed by redux.js.org
Cause 3 of 3
redux-persist dispatches its own actions
1Check
Persistence libraries dispatch their own actions and some store values like timestamps or Promises. Check whether redux-persist is in package.json.
grep -n "redux-persist" package.json2Fix
Ignore all the action types redux-persist dispatches.
import { FLUSH, REHYDRATE, PAUSE, PERSIST, PURGE, REGISTER } from 'redux-persist';
getDefaultMiddleware({
serializableCheck: {
ignoredActions: [FLUSH, REHYDRATE, PAUSE, PERSIST, PURGE, REGISTER],
},
})3Verify
Reload the app; persist actions no longer warn.
npm run devConfirmed by redux.js.org
How do I stop it coming back?
- Store IDs and ISO strings in Redux; build Dates and class instances at the edge where you need them.
- Leave the serializability check on; the Redux docs encourage keeping it active.
- When you must make an exception, name the exact path or action type.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix