Hi, is there a way to capture and run logic when the following is emitted from the config?

loginFailedMessage

. I am trying to debug how my application is getting into this state where the FullAppEmbed is replaced with the text provided in the config.

message has been deleted

I was able to see in the SDK lib that this happens from the Logout callback I believe. If someone could confirm for me though.

cc: @Ruchi Anand

Hi @alc-aaron When authentication fails, SDK emits an AuthStatus.FAILURE event with the failureType. That failure is what causes the FullAppEmbed to be replaced with the loginFailedMessage UI. You can capture it by listening to the auth event emitter returned from init():

const authEmitter = init({ ... });

authEmitter.on(AuthStatus.FAILURE, (payload) => {
  console.error("Auth failure", payload);
});

Ref : https://developers.thoughtspot.com/docs/Enumeration_AuthStatus#_success Let me know if that’s what you were looking for, or if you need more details.

I was looking at the SDK code and it appears that we emit the FAILURE and EXPIRY events even if it successfully recovers when getting a token? If this is true then should we have logic for retrying to fetch the sdk-token manually if that event is emitted or rely on the SDK to resolve that?

Could you tell us which authType you are using?

We are using cookieless authentication

Yes, that is expected behavior. When a token expires, the SDK handles token expiration and regeneration internally. The EXPIRY / FAILURE events are emitted for notification purposes, even if the SDK successfully refreshes the token. No manual retry logic is needed on your side, you can rely on the SDK to resolve it automatically.