This is so glaring to me, I'm shocked it's not been reported. I guess it's an edge case, really. How often do people throw errors in the next handler of a forEach on a synchronous observable? But still. It's CRAZY to me that this wasn't caught before. And even worse: I didn't catch it while updating the code, and it passed review! haha.