# Limits & errors

What the Attentive connection does not do, its limits, and the common errors when connecting or sending events.

## Limits

| Limit | Value |
|-------|-------|
| Attentive companies per profile | One |
| Events per request to Attentive | One, five requests at a time |
| Test mode | None |

## What you cannot do

- Send hashed emails or phones: Attentive needs the plain value to reach the person
- Retry an eCommerce event Attentive left unanswered: it carries no event id to dedup on
- Use quotes, brackets, braces, backslashes, pipes or commas in a custom event name
- Read Attentive subscribers or Journey results through Zernio

## Common errors

| Error | Cause | Fix |
|-------|-------|-----|
| `401` with `invalid_credentials` on connect | Attentive refused the key | Copy the key again from the custom app. |
| `403` on connect | The Ads add-on is off | Turn on the Ads add-on. |
| `409` with `profile_platform_conflict` | The profile already has another Attentive company | Disconnect it first, or use another profile. |
| A failure naming "Attentive needs" on an event | No usable match key | See [Conversions](/platforms/attentive/conversions#if-it-fails). |
| `401` with `reconnect_required` on an event | Attentive refused the saved key | Connect again with a fresh key. |

## Related

- [Connect](/platforms/attentive/connect)
- [Conversions](/platforms/attentive/conversions)
- [Rate limits](/guides/rate-limits)