When a connection fails, the setup screen shows the cause and the fix. This page lists the most common ones. The error code shown on the screen helps support find the problem quickly.
General
| Message | What to do |
|---|---|
| The sign-in link expired | The sign-in took more than 10 minutes or was opened elsewhere. Start it again from the same step. |
| The sign-in was closed | The provider’s window closed early. Start again; allow pop-ups for PALMS if it didn’t open. |
| The provider couldn’t be reached | Check your internet connection and retry in a minute. |
| Already connected | Open the channel in Settings → Channels; use Reconnect if it needs new credentials. |
| Connected to another organization | Disconnect it there first, or contact PALMS support. |
WhatsApp, Messenger and Instagram (Meta)
| Code | Meaning | Fix |
|---|---|---|
| 190 | The access token is no longer valid | Log in with Facebook again, or create a permanent system-user token. |
| 10, 200–299 | Permission missing or no access to the account | Give the system user Full control of the WhatsApp account; generate the token with both WhatsApp permissions. |
| 100 | Meta doesn’t recognise the details | Copy the IDs again (digits only). |
| 4, 80007 | Too many requests | Wait a few minutes and retry. |
| 368, 131031 | The account is restricted or locked | See Account quality in WhatsApp Manager; check the two-step PIN. |
| 133005 | Wrong two-step verification PIN | Turn two-step verification off for the number, or reset the PIN. |
| 133006 | The number isn’t verified yet | Verify it with the SMS or call code. |
| 133010 | The number isn’t registered | Use the guided connection, or register it in WhatsApp Manager. |
| 133015, 133016 | Recently deleted, or too many attempts | Wait (5 minutes, or a few hours) and retry. |
| 2655093 | Already shared with a partner | Ask the previous provider to remove their access; turn two-step verification off. |
| 2593109 | Chat history sharing was declined on the phone | Nothing to fix: new messages still arrive. To import the history, disconnect and connect again, and accept sharing in the app. |
Messages from the Facebook login (Embedded Signup)
| Message | Meaning | Fix |
|---|---|---|
| The Facebook login expired | Meta’s one-time code is valid 30 seconds and only once | Click Continue with Facebook again and finish in one go. |
| No number was shared | The window finished without a number (only the account was created) | Start again and add or choose the number in Meta’s window. |
| A different account or number was returned | The account or number isn’t one Meta shared with PALMS | Start again and pick the same account and number in Meta’s window. |
| The pop-up was blocked | The browser blocked Meta’s window | Allow pop-ups for PALMS (icon in the address bar) and try again. |
| Facebook’s login couldn’t load | An ad blocker, privacy extension or network blocks facebook.com | Turn the blocker off for PALMS, or try another browser or network. |
| Log in with Facebook isn’t switched on | The PALMS server has no Meta app settings | Ask your administrator, or use the Advanced connection. |
Website chat
| Problem | Likely cause | Fix |
|---|---|---|
| The bubble doesn’t appear | The code isn’t published yet, or a cache serves the old page | Publish the site in your website builder, clear the cache (plugin, CDN), then refresh. |
| The bubble doesn’t appear on one address | The address isn’t in the chat’s list | Edit chat → Your website: add the address (for example yourshop.cm). |
| “This chat isn’t available on this website” in the browser console | Same as above: the page’s address isn’t allowed | Add the address to the chat’s list. |
| The bubble appears for you but not for some visitors | An ad blocker or privacy extension blocks the chat | Nothing to fix on your side; most visitors aren’t affected. |
| PALMS says “Not installed yet” | No visitor has loaded the chat on your website since you pasted the code | Open your website yourself; PALMS notices within a few seconds. |
| Your replies don’t reach the visitor | The visitor closed the page | They see your replies when they come back on the same browser. Ask for an email in the pre-chat form to reply later. |
Telegram
| Code | Meaning | Fix |
|---|---|---|
| 401 | The bot token isn’t recognised | In BotFather: /mybots → your bot → API Token; copy it again. |
| 404 | The token is incomplete | Copy the whole token again, from the digits to the last character. |
| 400 | Telegram refused the request (often PALMS’s address for the bot’s messages) | Retry in a minute; if it persists, contact PALMS support. |
| 403 | The customer blocked the bot | Nothing to fix; they can tap Restart in the bot to write again. |
| 409 | Another program uses this bot | Stop it, or revoke the token in BotFather and use the new one. |
| 429 | Too many requests | Wait a minute and retry. |
| Token for another bot | Reconnect was given a different bot’s token | Use the token of the bot connected to this channel, or connect the other bot as a new channel. |
| Can’t reach this PALMS server | The server has no public https:// address | Your administrator sets PUBLIC_API_URL (https). |
| Messages stopped arriving | Another tool took over the bot (Telegram delivers to one place only) | Reconnect the channel; stop the other tool first. |
Messenger and Instagram
| Message | Meaning | Fix |
|---|---|---|
| No Page was shared | No Page was ticked in Facebook’s window, or the account manages no Page | Continue with Facebook again, choose Edit access and tick the Page. |
| No Instagram account was found | The account isn’t professional, isn’t linked to the Page, or wasn’t ticked | Switch to a professional account, link it to the Page (Edit profile → Page), then log in again. |
| You can’t message as this Page | Your role on the Page doesn’t include messaging | Ask a Page admin for full control or Messages access. |
| This channel’s Page wasn’t shared | On reconnect, the channel’s Page wasn’t ticked | Continue with Facebook, Edit access, tick the same Page and Instagram account. |
| The Facebook login expired | The Pages were chosen more than an hour after logging in | Continue with Facebook again and choose straight away. |
| 230 | The Page’s messaging permission was turned off in Facebook’s window | Continue with Facebook again and keep every permission ticked. |
| 190 | The Page’s access is no longer valid (password changed, role lost, PALMS removed) | Reconnect the channel with an account that manages the Page. |
| 551 | This person isn’t available right now | Nothing to fix; they can write to you again. |
| 10 / 2018278 / 2534022 | Outside the 24-hour window | Wait for the customer to write again. |
| Only your team gets answers | PALMS’s Meta app is in development mode or waiting for App Review | Expected until approval; see Approvals. |
| No Instagram messages arrive | “Allow access to messages” is off in Instagram | Instagram → Settings → Messages and story replies → Message controls → turn it on. |
SMS (Africa’s Talking, Twilio)
| Error | Meaning | Fix |
|---|---|---|
| Invalid API key | Wrong key or username, or sandbox vs live mismatch | The sandbox username is “sandbox”; generate the key in the same environment. |
| InvalidSenderId | Sender ID not approved | Request it in Africa’s Talking, or leave it empty. |
| InsufficientBalance | Not enough credit | Top up the account. |
| Twilio 20003 | Wrong Account SID or Auth Token | Copy them again from the Twilio Console. |
| Twilio 21211, 21614 | Invalid or non-mobile number | Use a mobile number in international format. |
| Twilio 21608 | Trial account | Verify your number in Twilio, or upgrade. |
| Twilio 21610 | The number replied STOP | Use another phone; reply START to subscribe again. |
| InvalidPhoneNumber | Africa’s Talking can’t read the number | Use international format with the country code, e.g. +254 712 345 678. |
| UserInBlacklist | The person opted out of promotional SMS | Use another phone for the test. |
| CouldNotRoute | No route to that network, or sender ID not approved there | Try another network, or ask Africa’s Talking support. |
| Twilio 20404 | Number or account not found | Click Find my numbers again and choose one. |
| Twilio 21606, 21408 | The number can’t send to that country, or the country is turned off | Buy a local number; tick the country in Messaging → Settings → Geo permissions. |
| No replies arrive (Africa’s Talking) | Callback URLs not pasted, or you send with a sender ID only | Paste both addresses in SMS → SMS Callback URLs; replies need a short code. See SMS → callbacks. |
Email (Google, Microsoft)
| Error | Meaning | Fix |
|---|---|---|
| access_denied | Sign-in cancelled or permission not ticked | Try again and allow reading and sending email. |
| invalid_grant | Authorisation revoked or expired | Sign in again. |
| AADSTS65001 | Your Microsoft 365 administrator must approve PALMS | Ask them to grant consent. |
| AADSTS50020 | Account from another directory | Sign in with the mailbox’s own work account. |
| AADSTS90094 | Only an administrator can approve PALMS | See administrator approval. |
| admin_policy_enforced | Google Workspace blocks unapproved apps | Ask your administrator to allow PALMS. |
| Password refused (IMAP) | Wrong password, or an app password is required | Create an app password. |
| IMAP switched off | The provider disables IMAP by default | Switch it on in the webmail’s settings. |
| Secure connection failed | Port and SSL don’t match | 993 with SSL (IMAP); 465 with SSL or 587 without (SMTP). |
| Use Continue with Microsoft | Outlook.com and Microsoft 365 refuse passwords from other apps | Choose Outlook and sign in with Microsoft. |
TikTok
| Error | Meaning | Fix |
|---|---|---|
| Region not eligible | Accounts registered in the EEA, Switzerland or the UK can’t use Business Messaging | Use an eligible TikTok Business Account. |
| access_denied | Sign-in cancelled or permission refused | Try again and allow all permissions. |
| Not a Business Account | Personal and Creator accounts can't use business messaging | In the TikTok app: Settings and privacy → Account → Switch to Business Account. |
| Permission missing (scope) | A permission was unticked on TikTok's screen | Connect again and leave every permission ticked. |
| 40001 No permission | PALMS's TikTok app isn't approved for this account yet, or the account isn't eligible | Check the account type and region; then contact PALMS support. |
| 40100 Too many requests | TikTok's rate limit | Wait a minute and try again. |
| 40105 / Sign-in expired | Access removed in TikTok, or unused for 30 days | Reconnect with the same account. |
| invalid_grant | The code from TikTok expired or was reused | Start the sign-in again. |
| Reply window closed | More than 48 hours since the customer's last message, or 10 replies already sent | Wait for the customer to write again. |
| Customers can't message you | Direct messages limited to friends or followers | TikTok app: Privacy → Direct messages → Everyone. |
LINE
| Error | Meaning | Fix |
|---|---|---|
| 401 Access token refused | The channel access token is wrong, was reissued, or belongs to another channel | In the LINE Developers console, open the Messaging API tab, issue the long-lived token again, and paste the whole token. |
| LINE couldn’t reach PALMS | LINE got no answer from the webhook address, or the channel secret doesn’t match | Check that the Channel secret is the one on the Basic settings tab, then retry. |
Viber
| Error | Meaning | Fix |
|---|---|---|
| 2 Token refused | The bot token is wrong, or the bot was deleted or isn’t active yet | Copy the token again from the bot’s page in Viber Partners. If the bot awaits Viber’s approval, wait for it, then retry. |
| Webhook not set | Viber checks the address by calling it, and the check failed | Retry in a minute. If it keeps failing, the PALMS server may not be reachable over https: contact support. |
Discord
| Error | Meaning | Fix |
|---|---|---|
| 401 Bot token refused | The token is wrong or was reset after you copied it | In the Developer Portal, open your application → Bot, click Reset Token, and paste the new token. |
Voice calls
| Error | Meaning | Fix |
|---|---|---|
| Number not in the account | The number isn’t one of the account’s numbers, or it can’t take calls | Enter the number exactly as the provider shows it (with + and the country code), or buy a number with voice. |
| Can’t receive from this provider yet | The server has no public https:// address | Your administrator sets PUBLIC_API_URL (https). |
The test message didn’t arrive
- Check you sent the exact code, to the right number or account.
- Wait a minute: some providers deliver with a short delay.
- WhatsApp: in WhatsApp Manager, check the number’s status is Connected. With the Advanced connection, the PALMS Meta app must be subscribed to your account (PALMS does this when connecting; Test on the channel rechecks it).
- Press Test on the channel in Settings → Channels: it shows the last time the provider contacted PALMS.
- Still nothing? Skip the test and contact support with the channel name and the time you sent the message.