Bug report: module state changes don't trigger API calls

I have a module ("user selector") that I use in a bunch of my apps.

I'm finding that while my Postgres resources get refetched then I select a different user, my Rest API calls do not. In fact, even changes to other non-module parameters that the Rest API call depends on won't trigger it to run again... until I remove the dependency on the module's data. I have triple checked that "Run query automatically when inputs change" is selected.

I realize this is a bit hard to explain and I'm reluctant to paste screenshots / provide too much data on this topic in a public forum. How else can I help you reproduce and fix the bug?

Patrick

I should add: I also tried adding a button to trigger the Rest query/resource on click, and that doesn't work either. As far as I can tell, it appears as if the resource is using stale state data from the module's exported data.

Hi Patrick,

I think it would be best for you to write in via chat support so that you are able to share some additional details, including screenshots/recordings.

You can access the chat support using the menu in the bottom right corner of Retool: