Internalize / Docs
Troubleshooting

Knowledge and routing problems

Separate a wrong route, a failed activation, expired hosting, and a genuine learning failure.

View as Markdown

When an answer does not reflect the taught knowledge, first establish which weights produced it. Adding the source to the prompt can hide the cause rather than prove the adapter works.

Check identity and timing

Compare the project selected by the key, the exact case-sensitive subject ID, and the inference job's adapter_version. Then inspect the learning job's candidate and activation result.

An inference admitted before activation keeps the previous version even if it completes afterward. A new subject starts from base. A key from another project refers to a different subject namespace. These cases can all look like forgotten knowledge while following the intended routing rules.

Candidate saved but inactive

ready means validation passed and a candidate was saved. If learning used activate: false, activation is still your release process's responsibility. If activation_conflict is true, another version changed while training.

Read the subject and review the candidate before manual activation. Do not automatically replace the expected-version value with whatever is current; that can overwrite another release. See Versions and routing.

Correct route, incorrect answer

Check whether the source actually contains the required fact, definition, or exception. The curriculum cannot ground a missing warehouse address or resolve two conflicting policies without a clear basis. Review whether the question asks for an application that was not adequately represented by the source.

Run several independent tests: direct recall, a paraphrase, an exception, and an unsupported question. Keep the source and expected answers out of the inference context. Inspect output truncation separately from factual correctness.

A passing built-in validation result covers its own checks, not all future behavior. Use the evaluation guide to decide whether to revise the passage, narrow the intended use, or restore a retained version.

Earlier knowledge changed

Later learning begins from active parent weights, but that is not a guarantee of perfect retention. Test old behaviors after updates. If several jobs were admitted from the same parent, their knowledge is not automatically merged; one candidate may omit another concurrent update.

Serialize dependent updates and retain a source manifest so you know what each release intended to add. A correction is a new learning operation, not verified erasure of an earlier fact.

Expired adapter

adapter_expired means the required retained state is no longer valid for routing or activation. Inspect expires_at and the current subject. The platform does not silently fall back to base or another user's adapter.

Contact support with the version and source job IDs. Restoration requires verified retained state; do not claim the knowledge remains hosted if that state cannot be recovered. Keep canonical sources outside the model so a deliberate rebuild is possible if needed.

On this page