Skip to main content
Channel errors occur when Fliqr AI cannot deliver a message or maintain the connection to a messaging platform. The cause is almost always one of three things: an expired authorization token, a policy violation on the channel provider’s side, or a configuration mismatch. This page covers the most common errors per channel and the steps to resolve each one.

​
Before You Start

Check Settings → Logs → Delivery for the exact error code returned by the channel provider. The log entry will include the provider’s error code and a description, which is more specific than the error badge shown in the channel list. [SCREENSHOT: Channel settings page showing a red error badge on a disconnected channel]
Most channel errors fall into two categories: authorization issues (fix by reconnecting the channel) and messaging policy issues (fix by adjusting the message content or timing). Check the delivery log first to confirm which category applies before taking action.

​
Errors by Channel

Message not deliveredThe most common cause is that the 24-hour customer service window has expired. WhatsApp only allows free-form messages within 24 hours of the last inbound message from the contact. After that, you must use a pre-approved message template.Fix: Use a template message block in your flow when sending outside the 24-hour window. If the contact hasn’t messaged in over 24 hours, the flow should use a template, not a text block.The second cause is that the contact has blocked your number. There is no way to override this — the contact must unblock you.
Template rejectedThe template was submitted to Meta for approval and was rejected because the content violated Meta’s messaging policy. Common violations include promotional language without the contact’s opt-in on record, misleading CTAs, and restricted content categories.Fix: Review Meta’s WhatsApp Business messaging policy. Edit the template content to remove policy violations and resubmit. Approval typically takes 24–48 hours.
Phone number not verifiedThe WhatsApp Business API phone number associated with your channel has not completed Meta’s verification process, or the verification has lapsed.Fix: Go to Settings → Channels → WhatsApp and follow the verification steps. You may need to re-enter the phone number in the Meta Business Manager and complete SMS or voice call verification again.
Permissions not grantedThe Instagram connection is missing required permissions — typically instagram_manage_messages or pages_messaging. This often happens after a Facebook security review or if the original authorization was done with limited scope.Fix: Go to Settings → Channels → Instagram and click Reconnect. When the Facebook authorization dialog appears, confirm that all requested permissions are granted. Do not uncheck any permissions.
24-hour window expiredLike WhatsApp, Instagram Messaging only allows replies within a 24-hour window from the contact’s last message. After the window closes, no further messages can be sent to that contact until they message again.Fix: Ensure your flows respond within the 24-hour window. If a contact needs a follow-up outside the window, Instagram does not currently offer a template-based re-entry mechanism equivalent to WhatsApp’s — you must wait for the contact to message first.
Page not connectedThe Facebook Page associated with your Messenger channel has been disconnected. This can happen if someone removed the Fliqr AI app from the Page’s connected integrations in Facebook Business Settings.Fix: Go to Settings → Channels → Messenger and click Connect via Facebook Login. Complete the authorization flow and re-select the Page. Confirm the connection status turns green before testing.
Message tag not allowedYou used a message tag (such as POST_PURCHASE_UPDATE or CONFIRMED_EVENT_UPDATE) on a message that doesn’t qualify for that tag, or you used a promotional message outside a permitted window.Fix: Review Meta’s Messenger Platform policy on message tags. Use tags only for their specified purpose. For subscription-style notifications outside the 24-hour window, your Page must be approved for Subscription Messaging.
Bot token invalidThe Telegram bot token stored in Fliqr AI is no longer valid. This can happen if the token was regenerated in @BotFather or if the bot was deleted.Fix: Open Telegram, message @BotFather, and use /mybots to access your bot. Select your bot, then choose API Token to view or regenerate the token. Copy the token and update it in Settings → Channels → Telegram.
Webhook conflictAnother application is registered as the webhook endpoint for the same bot token. Telegram only supports one active webhook per bot — if another service registered itself after you set up Fliqr AI, Fliqr AI’s webhook is no longer receiving updates.Fix: Ensure no other application (e.g., a staging environment, a competing bot service) is using the same bot token. In Fliqr AI, go to Settings → Channels → Telegram, disconnect and reconnect the channel to re-register Fliqr AI’s webhook endpoint.
Message undeliverableCarrier filtering blocked the message. Carriers filter messages that appear promotional when the recipient has not opted in, or messages from numbers not registered for commercial use.Fix: Verify that the contact has a documented opt-in record. Ensure your Twilio number is registered as a 10DLC number (for US traffic) or has the appropriate country-specific registration. Check Settings → Logs → Delivery for the specific carrier error code.
Invalid number formatThe phone number stored for the contact is not in E.164 format. E.164 requires a + followed by the country code and local number with no spaces or dashes (e.g., +15551234567).Fix: Update the contact’s phone number to E.164 format. If you imported contacts from a spreadsheet, check the import file for formatting inconsistencies and re-import after correcting the phone number column.
Twilio webhook failedThe Twilio voice webhook URL is either incorrect or Fliqr AI’s endpoint is returning an error. When Twilio can’t reach the webhook, calls drop or are not handled correctly.Fix: Log into your Twilio console and navigate to the Phone Numbers section. Find the number connected to Fliqr AI. Verify that the webhook URL in the “A Call Comes In” field matches the URL shown in Settings → Channels → Voice in Fliqr AI exactly. Update the Twilio webhook if there’s a mismatch, then place a test call.

​
What’s Next

FAQ

Answers to common questions about Fliqr AI setup and behavior.

Platform Limits

View rate limits, contact caps, and other platform quotas.