You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the desired behavior when an OAuth token is expired/invalid?
For example, I created a session, initialized a Resource and then called resource.Query() in a loop on a 5 second delay just to simulate some typical usage by an automated client.
I logged into my Org and removed the client's session.
SFDC returns INVALID_SESSION_ID: Session expired or invalid, obviously. Thus, an error is returned (I assumed via the call to queryResponse().
Is there anything besides the error string I could inspect if this occurs?
Am I missing functionality that you've already implemented?
Is there a benefit to re-auth and/or letting the caller know that they should authenticate and retry?
The text was updated successfully, but these errors were encountered:
What is the desired behavior when an OAuth token is expired/invalid?
For example, I created a
session
, initialized aResource
and then calledresource.Query()
in a loop on a 5 second delay just to simulate some typical usage by an automated client.I logged into my Org and removed the client's session.
SFDC returns
INVALID_SESSION_ID: Session expired or invalid
, obviously. Thus, an error is returned (I assumed via the call toqueryResponse()
.The text was updated successfully, but these errors were encountered: