If you add keepUnusedDataFor: 0 to course queries, then the new pagination with useAppDispatch works. However using this approach means refetching previously fetched data ( the client sends new http requests ). I think the issue has to do with shallow copying the new new pagination request, so redux thinks the query got the same input, meaning it will subscribe to the previous query with the same input, therefore not rerendering the ui.
If you add keepUnusedDataFor: 0 to course queries, then the new pagination with useAppDispatch works. However using this approach means refetching previously fetched data ( the client sends new http requests ). I think the issue has to do with shallow copying the new new pagination request, so redux thinks the query got the same input, meaning it will subscribe to the previous query with the same input, therefore not rerendering the ui.