# Troubleshooting

No contexts: set SOLUTIONLINK_CONFIG in the MCP host, use actual discovered context metadata and reload the entry. Offline tools and tool discovery work without a configured context; native tools need configuration and login.

Native application unavailable/not-ready or unauthenticated: stop the MCP, run npm run login and complete sign-in in its dedicated Edge window. Press Enter to verify and close it, then restart MCP. Do not copy cookies or restart unrelated browsers.

Profile in use: stop only the kit process that owns this dedicated profile. Do not delete profile locks or kill every browser. Different kit installations can use different dedicated stateDir values.

Identity/author/repository changed: inspect native state. Do not weaken the guard or replace configured IDs with values from an untrusted document. Ask the context owner if the change is expected, then update configuration within authorized scope.

Writes disabled: this is the default. Read and prepare offline/local previews first. Enable writes in your local config only for the authorized task and reload MCP.

Plan stopped/needs inspection: inspect journal and native records. Partial native changes may exist. Do not remove the journal and replay; prepare a reconciled new plan only after understanding the state.

NPV differs: read actual timed cashflows and stored discount rate. Native equal-month end-period NPV discounts period1 once. Convert annual rate with (1+r)^(1/12)-1, but verify stored native precision. Dated actual-days/365.25 NPV is a different convention. Distinguish capacity value from cash savings, and potential metrics from forecast amounts. Do not adjust benefits to force agreement.

eXplore link loops/blinks or iframe is blank: do not assume more sign-ins fix it. Verify host and supported launch contract, test top-level native link separately and ask the vendor about framing/session requirements. The kit provides no headless credential grant or embedding bypass.