Troubleshoot common problems

Resolve common sign-in, task, file, message-channel, plugin, MCP, and knowledge-base issues.

Use an enabled method and confirm the account is active.
Request a reset for a local password.
Restart SSO from the login page.
Wait for login protection to cool down instead of retrying continuously.

A task cannot start

Read the preflight message:

Choose another model if the selected one is disabled.
Remove or update an unavailable plugin or Skill.
Fix a missing or conflicting explicit credential binding.
Test the URL, authentication, and timeout of a required MCP server.
Select a knowledge base that is still enabled and accessible.
If your weekly credit quota is exhausted, wait for the next weekly reset or ask an administrator to adjust or manually reset it.

For provider access denials, rate limits, rejected requests, temporary outages or timeouts, follow the message and ask an administrator to check provider settings or connectivity. Administrators can run linksense logs runner, correlate the request and turn IDs, and inspect upstreamStatus, upstreamRequestId, protocolMode, model and failureCode on model provider request failed entries. Share only redacted diagnostic fields, excluding credentials, conversation content and complete upstream responses. Successful ordinary chat does not establish that multiple tool rounds work.

Updated management tools provide linksense doctor --network to check terminal downloads and Docker pulls independently; before installation, run --check-network with the bootstrap downloaded from main. For older releases such as v0.3.8 that lack this option, the bootstrap downloads the diagnostic helper at a fixed source revision to check the selected release without executing its installer. Re-download the bootstrap if an older local copy returns 64. Diagnostics can download images but do not execute containers or restart services. They do not verify provider-backed task execution.

Refresh and reopen the same task so LinkSense can recover the original turn. Do not submit repeated copies during a network interruption. Retry only after the turn has definitively failed.

When the model context window is exceeded, an ordinary task automatically attempts to continue once. If it ultimately fails, wait for the task to stop, compact its context, and state where work should continue. See Draft and context management.

If a plan decision cannot be submitted, check whether the task already entered a new turn, goal, or automation state; a stale decision cannot overwrite newer state. If branching fails, confirm that the source task has stopped, has no queued request, and is not archived.

Upload or preview fails

Check type, size, and batch limits.
Ensure the extension matches actual file content.
A preview failure does not necessarily mean the original is lost; try downloading.
For knowledge documents, inspect the failed processing stage and retry.

Search has no results

Help-center search is generated by a static production build and is not available in the development server. Product search returns only data your account can access.

A site cannot be published or opened

Only a registered, downloadable HTML task deliverable can be published. An ordinary attachment or a file that is still being generated cannot be used.
If styles, scripts, or images are missing, regenerate and register the complete web deliverable in the source task instead of uploading only the entry HTML.
If the link name is taken, choose another 3–80-character combination of letters, numbers, or hyphens.
A public link is unavailable after unpublishing, permanent source-task deletion, or owner-account deactivation.
Updating an unpublished site does not automatically make it public. Choose Republish under Resource library → My sites after the update.

See Publish and manage sites for the complete workflow and security boundaries.

The Feishu bot does not respond

Confirm that Feishu is connected under Settings → Message channels. Do not scan repeatedly while administrator approval is pending; the connection recovers automatically after approval.
Only one-to-one private text from the bot creator is accepted. Group chats, other people, and non-text messages do not start tasks.
A local deployment does not need a public callback, but the LinkSense environment must reach Feishu over HTTPS and WebSocket.
If Feishu says the application does not exist, use the Create a new application path to replace the deleted application instead of scanning the old QR code.
If an untitled task appears but never starts, refresh the task and channel status, then send one new short message instead of repeatedly submitting the original.

See Connect and use Feishu for connection, approval, disconnection, and recovery steps.

Weixin does not respond

Confirm that Weixin is Online under Settings → Message channels.
The message must come from the account that scanned the code and be supported text or transcribable voice.
If any QR, phone confirmation, or pairing-code step was not completed, reconnect and follow the current page.
Check credit quotas, maintenance state, and task concurrency. Do not repeatedly send the same message.

See Connect and use Weixin for connection and disconnection steps.

WeCom, DingTalk, and Microsoft Teams have different setup requirements. Start from the message channel overview and open the relevant guide. Only Teams requires a public HTTPS messaging endpoint.

Image generation fails

Confirm that an administrator enabled an image-generation model.
If the provider rejects the request, review the prompt, model, and credential configuration. If the service is unavailable, try again later.
Transparent backgrounds may require native support from the current model, especially for hair, glass, smoke, or other complex edges.
Do not immediately repeat a request after artifact-registration or usage-recording failure. The provider may already have processed and charged for it.

See Generate images.

Contact an administrator

For system health, model, authentication email, knowledge processing, retrieval, or runner errors, provide the time, page, stable error message or code, and safe reproduction steps. Never send passwords, tokens, API keys, temporary URLs, or sensitive file contents.