Connection errors

First checks

Connection errors can come from network problems, expired sessions, invalid credentials, or revoked access. Start with these checks before changing settings.

1. Reload the page and try the action again.
2. Confirm your internet connection is working.
3. Sign out and sign back in if the page has been open for a long time.
4. Note the exact error message and the page or tool where it appeared.

Browser or upload connection failed

Uploads go from your browser to Loam's temporary upload storage, then Loam creates a CSV target or loads the selected existing Table. A slow or blocked connection can interrupt that path.

• In the Add table dialog, choose Try again, then select the file again.
• Make sure the file is CSV, TSV, JSON, XLSX, or Parquet and no larger than 100 MB.
• If a firewall or VPN blocks the upload, ask your network administrator to allow Loam API and upload-storage requests.

API key connection failed

Each API key has its own resource allow and deny rules and is also bounded by its creator's current access. If a script cannot connect, check the key before changing the query.

• Open Settings > API keys (sign in to open this page) and confirm the key still exists.
• Make sure the key was copied without spaces or line breaks.
• Confirm the key has an allow for the resource and no explicit deny applies. Also confirm its creator still has access.
• If the key may have been shared or exposed, revoke it and create a new one.

AI tool authorization failed

Your AI tool uses Loam's configured MCP resource and OAuth account picker. If authorization fails, the tool cannot access your Loam data.

1. Open Settings > Connect AI (sign in to open this page) and copy the configured Loam MCP URL.
2. Paste that full configured URL into your AI tool. Do not add a workspace, Agent, credential, or endpoint suffix.
3. On the Loam authorization screen, sign in, choose My account or an eligible Agent, review the live access and restrictions, then click Allow.
4. If one existing connection still fails, revoke that authorization and reconnect it. This does not revoke the shared MCP resource, the selected Agent, another client, or another human's authorization.

Connected but data is missing

Review the connection's selected account and live access in Loam. The human or Agent must currently have access, no explicit deny may apply, and a human using an Agent must remain eligible to use it. These changes take effect without reconnecting the client.

Still blocked?

Open the Support button in the Loam sidebar. Include the exact error message and what you were doing when it appeared.