> ## Documentation Index
> Fetch the complete documentation index at: https://please.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Resolve common issues with the product preview and public simulation service.

## The web app shows balances or completed activity

The current app is an interactive demonstration. Portfolio values, returns, activity, responses, routes, and approval states are illustrative and are not connected to your wallet.

## A button does not submit a transaction

This is expected. The current public web product and MCP service cannot approve, sign, submit, or broadcast transactions.

## The MCP client cannot connect

Confirm that the client supports remote Streamable HTTP MCP servers and that the URL is exactly:

```text theme={null}
https://mcp.please.xyz/mcp
```

If your client requires an SSE-only endpoint or a `GET` connection to `/mcp`, it may not be compatible with the service.

## An action is unavailable

Call `discover_actions` again. Availability can depend on the action, network, asset, provider configuration, market or vault allowlist, and safety policy. Do not substitute a different asset, chain, address, or market without explicit user direction.

## The service asks for more information

Supply every material parameter requested by the client. A preview should not proceed with a guessed chain, asset, amount, recipient, beneficiary, market, vault, slippage, or fee limit.

## A simulation failed

A failed result is a hard limit, not a recommendation to proceed elsewhere with the same unreviewed transaction. Read the error and warnings, verify the inputs, refresh capabilities, and request a new simulation only after resolving the cause.

## The result expired or looks stale

Request a fresh preview. Do not rely on an old quote, state reference, or simulation after the engine or client marks it expired.

## My client displays a different result

AI clients may summarize tool output incorrectly or omit important warnings. Inspect the structured tool response when possible, including semantic steps, expected deltas, simulation mode, warnings, state reference, and expiry.

## I found a product or security issue

Contact [hello@please.xyz](mailto:hello@please.xyz). Include the page or client, the steps you took, what you expected, and what happened. Remove secrets and unnecessary personal information first.