104011: Session history fetch failed

Loading an AI Transport session's channel history failed after retries, so the messages needed to rebuild session state could not be retrieved.

What you should do

Inspect the cause for the underlying failure: it carries its own error code and tells you whether this is transient or needs fixing. The SDK already retried the fetch with backoff and exhausted its budget, so do not retry in a tight loop; if the cause was transient, retrying the affected history load later can succeed, but a persistent cause keeps failing until it is fixed. Until the load completes, the state it would have rebuilt is missing.

Why it happens

Rebuilding state, such as hydrating a session or loading older messages, pages through channel history. This error is raised when that paging fails after its bounded retry budget is exhausted, whether on the initial history request or on a later page. It is also used when a history load fails with an error that does not already carry its own code. The originating failure is preserved as the cause where available.

What you'll see

The error is reported with code 104011 and status 500. Messages take the form unable to fetch history page; ..., unable to fold channel history; ..., or unable to load older messages; ....