> For the complete documentation index, see [llms.txt](https://docs.flowflex.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowflex.ai/help/troubleshooting.md). # Troubleshooting Find the likely cause and the fix for common problems with flows, messages, broadcasts and channels. Each section below answers a common question. Most flow problems come down to three things: which version is published, how the flow is triggered, and the settings on the step where it goes wrong. Check those first. When Rangoli Store's order-update flow stopped sending messages, Alex Lee opened the flow and found that the latest changes were saved as a draft but never published. Publishing the draft fixed it. ## Why doesn't my flow start? Usually the latest changes aren't published yet, or the trigger doesn't match the event your system sends. 1. Open the flow and check which version is published. A saved draft isn't live until you publish it. 2. Open **Trigger** and confirm it uses the event you intended. 3. For a custom event, confirm your integration sends that event with the expected data. 4. For WhatsApp incoming chats, check that the right channel and incoming-message campaign are set up and published. See [Trigger setup](/workflows/triggers-and-variables.md) and [Publishing](/workflows/versions-and-portability.md). ## Why didn't my WhatsApp message arrive? Usually the destination number is wrong, the channel isn't available, the customer's reply window has closed, or the template isn't approved or is missing a required field. 1. Check that **Destination number** includes the country code and points to the intended customer. 2. Check that the connected WhatsApp channel is available. 3. For free-form messages, confirm the customer's reply window is still open. Outside that window, use an approved template. 4. For templates, check approval and availability, then fill every required placeholder and header field. 5. Review any delivery error shown in FlowFlex before you try again. A preview shows the message layout. It doesn't prove WhatsApp delivered it. See [Shared message setup](/workflows/whatsapp-message-setup.md). ## Why does a chat message show as failed? When a message can't be sent from **Conversations**, FlowFlex keeps it in the chat marked as failed, with a red icon. Hover over the information icon next to it to see the reason. Common reasons: * **Negative wallet balance:** agent replies can't be sent while your wallet balance is below zero. [Add message credits](/account/billing-and-wallet.md#add-message-credits), then send the reply again. * **Channel needs reconnecting:** the WhatsApp channel has to be reconnected. Go to **Channels** and reconnect it. See [Connect a WhatsApp channel](/whatsapp-setup/connect-channel.md#common-problems). ## Why can't I find my template? It may belong to a different WhatsApp account, not be approved yet, or be hidden by your search. Check that the template belongs to the WhatsApp account the flow uses, is approved, and matches your search. Clear the search and look under Marketing, Utility or Authentication. If it's still pending or was rejected, sort that out in **Templates** before you set up the node. See [Create a template](/whatsapp-setup/create-template.md) and [Template message](/workflows/nodes/template-message.md). ## Why is a variable missing or showing the wrong value? Usually the field isn't in the trigger sample or the API response example, or the flow uses it on a path where it has no value. Check the selected source, the nested field and the sample data. Add the field to the custom trigger sample or the API response example, and save it. For a captured reply, turn on response waiting on the question node. Don't use an answer on the **No response** path, or a success-only API field on its error path. See [Variable troubleshooting](/workflows/using-variables.md#if-a-field-is-missing). ## Why does my flow keep waiting, or take the No response path? The customer hasn't sent an answer the waiting node accepts within its time limit. Check the waiting node's **Unit** and **Value**. Button and List messages need a matching choice: a URL click or a reaction isn't an answer. A location request needs a shared location. With **Check format** turned on, an invalid answer may lead to another prompt. Connect **No response** to a reminder, an agent handoff, or **End**. See [Response waiting](/workflows/response-wait.md). ## Why can't I save my flow? Check that the flow has one **Trigger** and one **End**, no unused nodes, and a connection from every output shown. That includes button choices, list rows, conditions, **No response**, and every API outcome. Open any node that shows an error and fill in its required settings. See [Build and connect a flow](/workflows/building-a-flow.md). ## Why does my API request fail? * **Non-2xx response:** check the service's error response, the required credentials, and the request details. * **Request failed:** check the endpoint address and the timeout settings. * **JSON error while editing:** put quotes around variable placeholders, and check commas and brackets. Use the API drawer's request test with safe sample data. A test can change records in the connected service. See [API setup](/workflows/nodes/api.md). ## Why won't my file upload or send? Check the selected media type, the file format and its size. For a public URL, make sure the file opens without a login. For a file a customer uploaded, check the `assetId` and whether the file has expired. For **Upload new file**, wait for the upload to finish before you save. See [Choose files and media](/workflows/files-and-media.md). ## Why does my flow take the wrong condition path? Check the field type, operator, comparison value, and AND/OR groups. In a condition branch, the first matching path wins, so put specific rules before broader ones. See [Set conditions](/workflows/setting-conditions.md). ## Why doesn't a repeated sequence reach the result I expect? Check that the **Repeat until** stop condition uses the latest answer or API result. After **End loop**, route on whether the condition was met. Reaching the attempt limit doesn't mean the task succeeded. See [Repeat until](/workflows/nodes/repeat-until.md). ## Why didn't my broadcast reach everyone? Open the broadcast and check **Error Messages**. Each error shows Meta's code and what to do. See [Results and errors](/broadcasts/results-and-errors.md). Opted-out, invalid and duplicate contacts are skipped before sending. Contacts after the end date are never sent. See [Pre-send checklist and FAQ](/broadcasts/checklist-faq.md). ## Why does my channel show Disconnected or Limited? See [Common problems](/whatsapp-setup/connect-channel.md#common-problems) in Connect a WhatsApp channel. ## Ask for help Tell FlowFlex support the flow name, the label of the affected node, the published version, the error shown, and what you expected to happen. Include a screenshot with customer numbers, API keys and other private information hidden. ## See also * [Results and errors](/broadcasts/results-and-errors.md) * [Connect a WhatsApp channel](/whatsapp-setup/connect-channel.md) * [Response waiting](/workflows/response-wait.md)