> ## Documentation Index > Fetch the complete documentation index at: https://docs.dmly.io/llms.txt > Use this file to discover all available pages before exploring further. # Fix a silent Facebook Page or Instagram account > Your Page or Instagram account shows connected but nothing reaches the Inbox: the four causes, how to tell them apart, and which you can fix yourself. The channel shows as connected. You can send a reply out by hand. But when someone DMs your [Facebook Page](/channels/facebook-messenger) or [Instagram account](/channels/instagram), or comments on a post, nothing appears in the [Inbox](/inbox/overview) and no error appears anywhere either. On Facebook and Instagram there are four things that cause that, and from the outside they look identical: the profile reads as healthy and nothing happens. This page is how you tell them apart. This is the Facebook and Instagram version of the problem. [Fix no inbound messages](/channels/no-inbound-messages) covers the same symptom on WhatsApp, where the causes are completely different. **Being able to send proves nothing about receiving.** Sending and receiving use different wiring on Meta, so "I replied and it went through, so the connection is fine" is the single most common wrong turn on this page. ## Start here: has anything ever arrived? Open **Configurations → Reports** and select the **Logs** tab. Select **Filters**, set **Event** to **Messages** and **Status** to **Success**, and make sure the profile you're chasing is the selected channel. Every inbound DM writes one row here, reading `Inbound Facebook message from …` or `Inbound Instagram message from …`. See [Reading the Logs page](/troubleshooting/logs) if the filters aren't showing what you expect. | What you see | Where to go | | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Rows, but the bot never answers them** | Messages are arriving fine. Go to [your automations point at a profile that no longer exists](#cause-3-your-automations-point-at-a-profile-that-no-longer-exists) | | **Rows that stop at a certain date** | Something changed that day: the profile was removed and added again, or the same profile was connected somewhere else. Start with [the same profile is connected twice](#cause-1-the-same-profile-is-connected-in-two-workspaces) | | **No rows, ever** | Nothing has ever been delivered for this profile. Work down the causes in order | Also look for one specific error row while you're here. Set **Event** to **Errors** and **Status** to **Error** and look for `Inbound Facebook received for a profile with no channel` (or `Instagram`). That row is [cause 2](#cause-2-the-profile-has-nothing-behind-it-in-dmly) naming itself, and it is the only one of the four that announces itself in Logs. It shows whatever channel you have selected, so you don't need to hunt for it. ## Cause 1: the same profile is connected in two workspaces A message from Meta says which Page or Instagram account it is for. It does not say which DMLY workspace it is for. So if the same profile is connected in two workspaces, DMLY has to choose one, and everything (the Contact, the conversation, the automations) happens there. The other workspace sees nothing at all, with no error, because as far as it knows nobody wrote to you. The copy that wins is the most recently connected one whose connection is still valid and has a working Channel behind it. That's why this often starts on the day somebody connected the Page somewhere else. It usually happens one of three ways: an agency connected a client's Page in the agency's own workspace as well as the client's, someone connected the Page in a second workspace to try something out, or an old workspace nobody uses still has it. **You can fix this yourself.** Disconnect the profile from the workspace that shouldn't have it (**Integrations → Channels**), and inbound starts landing in the one that should. Check every workspace you have, not just the one you're standing in. You can only see the workspaces you belong to. If the profile is also connected in an account belonging to someone else (a previous agency, a marketing contractor, an ex-employee's own workspace), you cannot see that from here and cannot disconnect it. That is the one case to take to DMLY support: say which Page or Instagram account it is, and that you think it is connected elsewhere. ## Cause 2: the profile has nothing behind it in DMLY A connected profile needs a Channel behind it before anything can happen. When that link is missing, Meta delivers the messages and DMLY has nowhere to put them: comments are dropped outright, and DMs land in a thread no automation can pick up. It looks exactly like a profile that is connected and reacts to nothing, because that is what it is. The tell is the error row named above: `Inbound Facebook received for a profile with no channel`, which also tells you the fix in its own words. **You can fix this yourself.** Connect the profile again: **Integrations → Channels**, the same tile you used the first time, and pick the same Page or account. See [Connect a Facebook Page](/channels/facebook-messenger) or [Connect Instagram](/channels/instagram) for the steps. That rebuilds the missing link and asks Meta to start delivering again. **Connecting again is not the same as the Reconnect button.** DMLY only offers **Reconnect** on a profile once it knows the connection has broken. A profile that is silent but still looks perfectly healthy won't show one, so the way to re-run the connection is to add the same Page or Instagram account again from the tile you used originally. It updates the profile you already have rather than adding a second one, so you won't end up with a duplicate. ## Cause 3: your automations point at a profile that no longer exists This is the one where messages *do* arrive and the bot still says nothing. Every automation is tied to the Channel it was built on. If a profile is disconnected and then added again, DMLY files it as a new Channel, and the automations built on the old one still point at something that isn't there. They match nothing, forever, and nothing reports it as an error, because as far as the bot engine is concerned this profile simply has no automations. The tell is on the **Automations** list: it only ever shows the profile you currently have selected, so automations tied to the old record disappear from the list altogether. If your flows seem to have vanished after you removed and re-added a profile, they haven't been deleted, they are attached to the old record. **You can fix this yourself, but it means rebuilding.** No screen moves an automation from one profile to another, and an orphaned one won't appear in the list for you to open, so build it again with the current profile selected. If it's a large flow you'd rather not rebuild, ask DMLY support before you start: tell them which profile you re-added, and roughly when. Avoid this next time: never disconnect a profile first. Adding the same Page or account again on top of the existing one keeps the same Channel, and your automations stay attached. It is disconnecting and starting over that orphans them. ## Cause 4: the account was never subscribed to receive anything The signature here is absolute silence: not one message has ever arrived since the day you connected the profile. Sending can still work, which is what makes it so confusing. Connecting a profile does two separate things: it stores the credentials that let DMLY send, and it asks Meta to start delivering that profile's messages. If the second half didn't take, you get a profile that sends fine and never receives. **On Instagram** this is the common one, because Instagram messages are delivered through the Facebook Page your Instagram account is linked to, not through the Instagram account itself. If DMLY couldn't work out which Page that is at the time you connected, there was nothing to ask, so Meta has never sent anything. **On a Facebook Page** it happens when Facebook refused the request, which is usually a permission that was declined on Facebook's own approval screen. Declining any one of the messaging permissions is enough to leave the Page connected and silent. **You can usually fix this yourself.** For Instagram, first confirm in Meta Business Suite that your Instagram professional account is linked to a Facebook Page and that you're an admin of that Page. Then, for either, connect the profile again from **Integrations → Channels** and approve every permission Facebook asks for. Connecting works the Page out again and re-asks Meta to deliver, so the action is the same one as for cause 2. If you have done that and a full day passes with still nothing, stop retrying and contact DMLY support. Tell them: which profile it is, that no message has *ever* arrived, and that you have already reconnected and (for Instagram) confirmed the Page link. That is enough for them to check the delivery side, which isn't something you can see or change from your account. ## Which one do I have? | What you're seeing | Cause | Yours to fix? | | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------- | | DMs appear in the Inbox, the bot never answers, your flows are missing from the Automations list | [3](#cause-3-your-automations-point-at-a-profile-that-no-longer-exists) | Yes, by rebuilding the automation | | An error row saying a profile has no channel | [2](#cause-2-the-profile-has-nothing-behind-it-in-dmly) | Yes, connect it again | | Messages arrived until a date, then stopped, and the Page is connected in more than one workspace | [1](#cause-1-the-same-profile-is-connected-in-two-workspaces) | Yes, if the other workspace is one of yours | | A profile that has never delivered a single message since the day you connected it | [4](#cause-4-the-account-was-never-subscribed-to-receive-anything) | Usually, by connecting again and approving every permission | | None of the above, and Logs is completely empty for this profile | Take it to support | No | Before you decide it's none of them, check the boring one: your automation has to be **Active**, not a draft, and its trigger has to match what people are actually sending. See [Automation not triggering](/troubleshooting/automation-not-triggering). ## Next The same symptom on WhatsApp, where the causes are different. Which filters show inbound rows, and what each row means. What syncs to the Page, and what Messenger can send. Why Instagram connects through a Facebook Page in the first place.