Mark Erikson

If it helps, I just got a replay recorded: https://app.replay.io/recording/rtk-3795-addmatcher-swallowing-an-an-error-in-a-reducer--dd7a6a80-fe98-49f9-a1a4-a39f3d5fe4bd

Weird. It _looks_ like the error goes all the way back up to the stack... and then gets swallowed by an `async`-to-generator-transpiled body in `redux-toolkit.esm.js`?

And if I re-record the example with 2.0-beta.2 (which uses real `async`), it seems like we just unwind the stack out to `createAsyncThunk` and it vanishes: https://app.replay.io/recording/rtk-3795-error-in-a-reducer-rtk-20-beta2--35fad959-c1d4-4ce2-8365-dabf3340ee6e I'm actually pretty...

Ah, interesting. I assume that's to avoid repetitive console logs about uncaught errors. Like I said, _nothing_ can fix the "stuck pending" problem. The reducer was supposed to update the...

> What should my Redux state be after a reducer throws an error? Do we expect it to stay as it was before the reducer ran Yes, exactly that. The...

Btw, not sure I actually got this detail: what _was_ the actual error that was happening in your real code to cause this originally?

I was doing a cleanup sweep through our issues list and trying to close anything that looked resolved or unactionable. Yeah, as we've discussed, there's nothing that can be done...

@AndreaDigiTrails based on your description I'm not sure you're seeing the same problem described in this issue. That snippet isn't enough to actually give me any sense of what might...

I'll try to find some time to review it in the next few days. Good to know that A) it's useful, and B) the approach appears to be working -...

Out in https://github.com/reduxjs/redux-toolkit/releases/tag/v2.11.0 ! Thanks!