It's unclear to me why it's important that actions be fire-and-forget.
Is there no scenario in which you would want to show (next to the Favorite button) that favoriting failed but not care about other article-update failures?
Is there no scenario in which you would want to show (next to the Favorite button) that favoriting failed but not care about other article-update failures?
The importance of keeping actions fire-and-forget is that data must live in the store; if actions have callbacks, the views would be using state to keep themselves updated with data that should be in the store.