redux-saga: Sagas aren't being triggered, EFFECT_TRIGGERED only at startup

I had sagas set up in my app, handling side effects. I hooked up the saga middleware to my store, passing in the rootSaga, and was successfully executing a side effect in response to an action. I committed this code, then proceeded to add another side effect to respond to a different action. This worked as well, and I committed it.

Now when I run my code, at startup I see EFFECT_TRIGGERED twice followed by EFFECT_RESOLVED twice, but other than that, the sagas are never triggered in response to the actions they’re set up to watch. I thought that was bizarre, so I reverted to a previous commit where I know the sagas’ side effects were working, and it too has this odd behavior. I then reverted to the first commit where I set up sagas, and it too isn’t working.

Do you have an idea what could cause such behavior? I’ve compared my sagas and store to those in the examples, and they look fine. Since my saga and store code were working fine before, but stopped working (without me changing them, or any underlying libraries), I’m thinking the issue has to be caused by something related to my development environment. I tried setting up the development environment of the app on a different computer, reinstalling node_modules from scratch, and it’s having the same issue. If you have any idea what could be causing this issue, I’d greatly appreciate it.

I’m using redux-saga 0.9.1