In our application, we very often run into users being greeted with pages that do not have any of the data populated. It is similar to how the page looks when the authorization token has expired. Initially this is what I thought the problem was (even though they were not being greeting with the authenticate resource popup) and instructed them to login with an auth button in our application. However, they have to do this extremely frequently which is problematic. Anyway, when they are greeted with the unpopulated page reloading the page will actually then work and the data will get populated. No need for them to relogin. So it is basically like the Salesforce resource queries sometimes just do not run on page load.
For reference this is what our page would look like when the data is not being populated:
These users experiencing these problems do have use access to our Salesforce resource and it will pull in the information after a reload and for a brief period after when users go to the page again but after some time they will once again be greeted with no data populated and need to refresh the page. This happens to me as well on occasion as the admin.
I had a user open the dev console in their browser to see if there were any errors and they did report back a log with some 400 errors. The 403 errors make sense I suppose as that user just does not have access to those queries in the 403 errors. But the 400 error queries they do have access to and will load for them on a refresh: (the component is orphaned stuff is not relevant, something I need to fix down the line haha)
I will sometimes come up against this data not populating as well, though when I open the console, I do not see any direct 400 errors but looking at the network tab I do see that no get requests were ever made. It will just be one post request whereas when the app is functioning there will be a number of requests:
It feels like the user is just timing out way too soon and then clicking reload is "reauthorizing" and allowing the queries to go through.
I am using the cloud version of Retool so it does not seem there is any way to really control when users would need to reauthorize in Salesforce but they are never being told they need to reauthorize. The data just won't load frequently until they refresh and then the queries will activate. Not sure if this is just a strange thing with Salesforce integration on the cloud version. Salesforce can definitely be strange.
Thanks for any help and sorry for the long post just at a bit of a loss on what is directly the issue here and how to resolve it so users don't have to be constantly refreshing.