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

# Known issues

> Current limitations in DMLY that behave as designed, and where to go when something looks broken instead.

These are limitations that work exactly the way they were built, not faults. If you hit one,
there is nothing to fix on your side — but knowing about it saves you an hour of hunting.

If what you are seeing is not on this list, it is more likely a setup problem than a
limitation. Start with the pages at the bottom of this page.

## Mercado Pago

<Note>
  These apply to Mercado Pago only. Other payment gateways are unaffected — see
  [Payments and gateways](/finance/payments-and-gateways).
</Note>

<Accordion title="A payment link can be paid more than once">
  A Mercado Pago checkout link stays usable after it is paid. If someone pays against the
  same link a second time, DMLY reconciles that payment onto the **same** payment record
  rather than creating a new one — the second payment does not show up separately.

  Send a fresh link for each amount you want to collect, rather than resending an old one.
</Accordion>

<Accordion title="A partial refund still shows as paid">
  Mercado Pago does not change a payment's status when only part of it is refunded, so the
  payment keeps showing as succeeded in DMLY. Check the refund in your Mercado Pago account
  for the true amount.
</Accordion>

<Accordion title="You cannot charge a saved card">
  Mercado Pago runs through Checkout Pro, which always sends the customer to a checkout
  page. Charging a card you already have on file is not supported for this gateway — every
  payment needs a link the contact opens themselves.
</Accordion>

## Currencies you can use for payment links

Payment links support a fixed set of currencies: USD, EUR, GBP, CAD, AUD, NGN, GHS, ZAR,
KES, INR, AED, SAR, QAR, EGP, BRL, MXN, SGD, HKD, ARS, COP, PEN and UYU. Anything outside
this list — including Chilean peso, Japanese yen, Kuwaiti dinar, Bahraini dinar and Omani
rial, which don't use two decimal places — cannot be used for a payment link.

If your currency isn't on the list, take payment outside DMLY and record it manually. See
[Payments and gateways](/finance/payments-and-gateways).

## AI providers don't all do the same things

Which AI provider you connect changes what your AI replies can do.

|               | Knowledge base | Web search |
| ------------- | -------------- | ---------- |
| OpenAI        | Yes            | Yes        |
| Google Gemini | Yes            | Yes        |
| Claude        | No             | Yes        |
| DeepSeek      | No             | No         |

A knowledge base (documents your AI can search when it replies) works only with **OpenAI**
or **Google Gemini**. If you connect Claude or DeepSeek, there is no knowledge base to set
up — the option is not available for those providers.

<Note>
  AI depends on your plan. If the AI tiles show **Plan locked**, see
  [Plans](/billing/plans).
</Note>

See [Knowledge base](/integrations/knowledge-base) and [AI replies](/automation/ai-replies).

## Something else is wrong

Most problems are configuration, not limitations. Try these first.

<Columns cols={2}>
  <Card title="No messages arriving" icon="inbox" href="/channels/no-inbound-messages">
    A channel says connected but nothing reaches the Inbox.
  </Card>

  <Card title="Messages not sending" icon="paper-plane" href="/troubleshooting/messages-not-sending">
    A reply or notification never reached the contact.
  </Card>

  <Card title="Automation not triggering" icon="bolt" href="/troubleshooting/automation-not-triggering">
    A flow doesn't run when you expect it to.
  </Card>

  <Card title="Logs" icon="list" href="/troubleshooting/logs">
    See what your workspace actually did, and when.
  </Card>
</Columns>