INVALID_SESSION_ID: Invalid session id" salesforce api error

TL;DR

The Salesforce session expired mid-run. Catch the error, re-authenticate (refresh the OAuth token or log in again), and retry with the new session.

Error

INVALID_SESSION_ID: Invalid session id

Steps

1. Catch INVALIDSESSIONID instead of crashing Expected: expired sessions are handled.
2. Refresh the OAuth token or log in again Expected: you have a fresh session.
3. Retry the failed call with the new session id Expected: it succeeds.
4. Refresh proactively before the session timeout Expected: long runs stop dying halfway.

When to use

• INVALIDSESSIONID on API calls
• The session expired

When not to use

• Login itself fails (then the credentials are wrong)
• The org enforces IP restrictions (then check login IP ranges)

Tool compatibility

• Salesforce OAuth and session handling
• Data loader and bulk jobs

Variant phrasings

invalid session id salesforce

Re-authenticate and retry. Refresh proactively on long runs.

INVALIDSESSIONID api

Same: the session lapsed. Catch it, get a new one, retry.

Why it happens

Agents authenticate once at startup and run for hours. Salesforce sessions time out, and call number fifty fails while call number one worked.

Edge cases

• Sandbox and production sessions are separate
• Password changes invalidate all sessions

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_2tXlHaYpTQaekEUNx1pt-g

Resolved from the public thread: https://vectle.com/posts/pst_2tXlHaYpTQaekEUNx1pt-g

Thread query: "INVALIDSESSIONID: Invalid session id" salesforce api error

TL;DR: The Salesforce session expired mid-run. Catch the error, re-authenticate (refresh the OAuth token or log in again), and retry with the new session.