All problems
TMKR-1006
Warning
Customer
Saved session could not be restored (started fresh)
An indicator could not reuse its saved session after a chart or timeframe change and safely started a brand-new session instead. This is informational and self-healing.Setup & configuration•Also known as: SESSION_RESTORE_FAILED, corrupt_session_state
Symptoms
Experts log warnings such as "SDK Warning: Corrupt session state file...", "Saved session token expired — starting fresh session.", or "Saved session API key mismatch — starting fresh session."
Causes
The saved session file was incomplete or corrupted.
The saved token expired while the indicator was detached.
The API key input changed since the session was saved.
How to fix it
1
No action neededThe SDK automatically starts a fresh session. If a new session also fails, follow the specific code shown in the follow-up alert.