# Troubleshooting

Start with a read-only query and the exact error. Never paste passwords or tokens into a support message.

## Cannot connect

- Check HTTPS and the full /mcp path. The marketing website is not the MCP server.
- Use the same app/tenant origin throughout OAuth and requests.
- Verify that the client supports Streamable HTTP and OAuth with PKCE.
- Remote cloud clients cannot reach localhost without an explicitly configured secure transport.
- If a browser blocks the native callback, keep the error and client version; do not disable browser security.

## A tool is missing

Refresh tool discovery and start a new conversation. Reauthorize for the right purpose if necessary. Admin tools also require business roles. Old compatibility aliases were removed.

## Approved, but not submitted

Approval automatically executes the operation; there is no need to relay approval to the AI. Refresh the operation details and check queued, running, succeeded, failed or unknown status. The AI can query the original operation_id. Dispatch retries happen only before consumption, at most three times and within the original expiry. For an unknown outcome, inspect business records before requesting a replacement.

## Text field received a number

Follow the schema and provide a JSON string. Plain phone text should not contain embedded quote characters. Invalid collection input is rejected before approval. Correct the input before requesting a new operation.

## Expired or already used

Do not automatically replace the intent. Check whether the business result already exists, then ask the human whether to request a new confirmation.

## No form rendered

MCP Apps UI is optional. Open the returned browser URL or submit schema-correct values conversationally.

## What to send support

Contact service@sanctris.com with client name/version, approximate time and timezone, workspace ID, operation ID and the sanitized error. Do not send passwords, tokens or unnecessary form personal data.