> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/guides/messages-not-arriving-after-onboarding.md).

# Channel is Ready but no inbound messages or webhooks arrive (error 131070)

The channel is Ready or Live but no inbound messages or webhooks arrive, health\_status says the app is not subscribed, or replies fail with error 131070.

## Symptoms

This affects phone numbers that were already on the WhatsApp Business Platform with another provider (or directly with Meta) before 360dialog was added. The channel shows **Ready** or **Live** in the 360dialog Hub and webhook URL is set, but one or more of these happen:

### No inbound messages or webhooks arrive

Incoming messages, status updates and other webhook events don't reach 360dialog, so nothing reaches webhook URL. They still go to the previous provider.

### health\_status says "Your app is not subscribed to the message webhook"

The health check for the number reports that 360dialog's app is not subscribed to the message webhook, even though the phone number and account webhooks are set and return 200.

### Free-form replies fail with error 131070

Service (free-form) messages are rejected with error **131070**: `(#131070) Message failed to send because another app is controlling this thread now`.

## Why it happens

Under Meta's new account model, a phone number can be connected to more than one provider at the same time. The phone number sits in the **WhatsApp account (WAAC)**, and each provider has its own **Messaging account** (formerly WhatsApp Business Account, WABA) for the number. Meta decides which provider receives incoming messages and replies in a conversation. This setting is called **conversation routing**.

When the phone number is added to 360dialog, Meta keeps the existing routing. The previous provider stays the responder until the business changes it. 360dialog can't change this, and re-setting the webhook or repeating the onboarding doesn't fix it.

## Fix: route conversations to 360dialog

Only an admin of the Meta Business Portfolio that holds the WhatsApp account can do this.&#x20;

{% stepper %}
{% step %}
Go to [Meta Business Suite](https://business.facebook.com/latest/) > **Business settings** > **WhatsApp accounts**.
{% endstep %}

{% step %}
Select the WhatsApp account that holds the phone number.
{% endstep %}

{% step %}
Open **Conversation routing**.

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FGsA0mvFy0wA8x1WiR6t0%2Fanother.app.is.controlling.the.flow1.png?alt=media&amp;token=b063b503-5d0a-49e3-81ee-97bcb16bcd6a" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select **360dialog** in every dropdown.

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FoHbYXtH9OOcY7g95mcF2%2Fanother.app.is.controlling.the.flow2.png?alt=media&amp;token=cd7eb368-5437-4613-9db4-2fda002a7cb7" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Apply**.&#x20;
{% endstep %}
{% endstepper %}

Then send a test message to the number from the phone. It should reach webhook URL, and free-form reply should go through.

## Still not working?

If conversation routing already points to 360dialog and messages still don't arrive, contact 360dialog Support with the phone number, the health\_status output and the full error response.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.360dialog.com/docs/guides/messages-not-arriving-after-onboarding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
