basic question: possible to reduce API calls when loading objects following login about soqlx HOT 2 CLOSED

yes, it's technically possible, but the cache would get increasingly out of date. Checking/bringing it upto date would burn the same number of API calls anyway. Large org's tend to end up with large API limits, so I'd be surprised to hear that the <100 used to describe all the metadata causes an issue.
Can you explain your starting query timeout some more? I haven't seen any timeouts while running queries while the describe is ongoing. The 2 shouldn't interfere with each other on either the SoqlX side, or on the salesforce side. (Assuming the network connection from the client isn't heavily constrained).

All that said, the easiest answer to this is to not close the app. It'll keep the metadata cached, and the session will be automatically renewed if it expires. So you can leave the app open indefinitely and it'll continue to work next time you run a query.

from soqlx.

Thanks a lot for your answer (sorry for my delayed reply). I appreciate your advice.

About the starting query issue, thanks for mentioning about your experience - based on your that, I'll monitor it more closely & reopen if it becomes an ongoing problem. It may be possible that I had network issues.

from soqlx.