When a message arrives, the Historial (History) tab logs what happened, including the exact reason if no reply was sent. This table collects the most common reasons.
General reasons
| Message | What it means | What to do |
|---|---|---|
| No rule matches | None of your rules had a trigger that matched that message | Review your rules’ matching, or add an AI rule with “Any” scope to cover what doesn’t match anything |
| The rule doesn’t send a reply | The rule matched but is deliberately set to “No reply” | Normal if you use it only for a submenu or an alert |
| The reply was empty | The rule was about to reply but the text ended up empty | Check the reply text in the rule’s editor |
| Rule paused in this chat | That rule already fired recently in this chat and its pause hasn’t ended | Expected behavior of the pause; lower the pause time if you want it to reply more often |
| The rule repeated too soon | It fired several times in a row in a short time and Yammbot stopped it | Check “Prevent repeated rules” in Settings |
| Replies paused | The general auto-reply switch is off | Turn it on from Home or Settings |
| Channel disabled | That app’s channel isn’t active in Yammbot | Enable it under Channel apps |
| Ignored chat | That chat is on your ignore list | See Ignored chats |
| Matches “Don’t reply if” | The message matched an exclusion condition you set | Check “Don’t reply if” in Settings |
| Didn’t reply because you’re handling this chat | The chat is paused by takeover | Wait for the pause to end or tap “Resume” in Paused chats |
| Groups aren’t allowed | A group message reached a rule that only replies to individual chats | Change “Recipients” to Groups or Both — see Apps, accounts and groups |
| The notification doesn’t allow a reply | The notification arrived without a “Reply” button, so Yammbot can’t answer it | Check whether the chat is open on screen, or whether that app isn’t supported yet |
| Canceled before sending | Another rule canceled this reply before it went out (“Cancel pending replies”) | Expected behavior if you set that option |
| No connection | The phone had no internet at that moment | Check the phone’s connection |
| Timed out | Sending took too long | Usually resolves itself; check your connection if it keeps happening |
| Couldn’t send | The reply failed to send through the messaging app | Check that app is working normally |
Account and access reasons
| Message | What it means | What to do |
|---|---|---|
| Message reached an account Yammbot doesn’t reply on | The message arrived on an account you didn’t enable | Check which accounts are enabled in Channel apps |
| [Rule] matches, but didn’t reply: missing [detail] | The rule needs a My business detail you haven’t filled in yet | Fill in that detail under My business |
| The notification no longer allowed a reply (the chat was opened or deleted) | You opened or deleted the chat before Yammbot could reply | Expected behavior; Yammbot needs the notification to stay active |
| No access: your free month ended | Your trial ended and you don’t have an active plan | Choose a plan under Plan, payments and billing |
| No access: this phone already used the free month with another account | This phone doesn’t get a free month for the new account | Choose a plan to keep using Yammbot |
| No access: not signed in or your plan isn’t active | You’re not signed in to the app, or your plan isn’t active | Sign in and check your plan |
| No access: it’s been more than 7 days without being able to check your plan | The phone has gone over a week without connecting to check your access | Connect the phone to the internet |
AI errors
| Message | What it means |
|---|---|
| AI error | Groups together any failure from the AI provider while generating the reply |
See the full table of AI errors, with cause and fix, in AI assistant › Common errors.
Webhook error
| Message | What it means | What to do |
|---|---|---|
| Webhook error | Your server didn’t respond, returned an error, or returned something that isn’t valid JSON | Check the URL, user and password in Webhook, and that your server is reachable |
Yammbo POS error
| Message | What it means | What to do |
|---|---|---|
| POS error | Yammbo POS didn’t respond or the connection is no longer valid | Test the connection with Probar conexión (Test connection) on the Yammbo POS screen; if the code is no longer valid, pair again from your Yammbo POS panel — see Connecting Yammbo POS |
Where you see these reasons
In the Historial (History) tab, every entry shows “Reason: [text]” when no reply was sent. You can also filter the history by channel or show only priority alerts.