Troubleshooting

Check the station, then the model, then the action. Keep the error and execution status visible while diagnosing a failed request.

Chat cannot reach the station

Run railcall version and railcall doctor. Start the station with railcall studio and keep its terminal open. Studio normally listens on 127.0.0.1:8799; use the session-gated URL printed by the running station.

If the command is not found, open a new terminal or check that ~/.railcall/bin is on PATH. If the port is occupied, identify the existing station or service before stopping anything. The separate daemon on port 8555 does not replace the Studio server that Chat uses.

An update did not change behavior

Updating Chat and updating the station are separate operations. Stop a station you launched in a terminal with Ctrl+C, run the installer again, and restart it. If it runs as a service, restart that service. Check the version before retrying. Chat 0.12.6's PDF and Builder fixes require station v1.5.24.

A model is missing, slow, or unavailable

Use railcall models list to check local models. Start Ollama if necessary; use railcall models suggest with the station running to check hardware suitability. A model download is not a completed reasoning test.

For a collaborator, check membership, grant validity, allowance, holder presence, and that the holder's model is running. For BYOK, check supported provider access in Studio without sharing the key. For hosted Assistant, sign in with railcall market login and check the picker's availability message. Queue limits and worker downtime can prevent admission.

For complex tasks, inspect routing and local-only policy. Do not repeatedly resubmit a waiting action: check its status first to avoid duplicate work.

The reply says PDF, but no file appeared

Look for the export result and open the actual file. A content draft is only an intermediate result. On an older station, update before retrying an export that reports _agent_turn. If export still fails, keep the exact error, chosen route, and versions. Do not describe the PDF as generated until it opens.

A workflow stops or cannot be saved and run

Check that every step has a supported command binding, all required inputs are supplied, and credentials are configured. The documented Save & run path handles linear command-bound builds. A missing binding or unsupported branch needs correction; it is not a completed run. Check Sends for an action waiting on human approval.

macOS rejects an installer

Use a current installer from Chat downloads, matching your Mac's chip. If a download is incomplete, download it again. Report the exact macOS message and installer filename if rejection persists. Do not disable Gatekeeper to work around a release problem.

Send a useful bug report

Include Chat and station versions, operating system, selected route, a minimal non-sensitive request, expected outcome, exact error, and whether an artifact or receipt exists. Remove keys, session URLs, personal data, and private document contents. Contact sami@railcall.ai.