360Dialog - Geschichte beachten

We are seeing that a small percentage of stacks are still having issues related to the incident reported by Meta on Tuesday.

The clients affected by the issue get errors similar to {"error":"HTTPSConnectionPool(host='x', port=443): Read timed out. (read timeout=20)"} and {"meta":{"version":"v2.39.4","api_status":"stable"},"errors":[{"code":1014,"title":"Internal error","details":"Connection timed out. Please check if wacore is running: 10.0.14.50:6250"}]}.

We are in contact with Meta's support to find the underlying causes and fix the issue. If you are affected by this issue, please create a Support Ticket with us (Category: Messaging Has Completely Stopped Working) and we will prioritize the restart for you.

We are aware of an issue that is impacting the Template Creation Process. Our engineering team is currently investigating it and we'll update again as soon as possible.

Due to a problem with Meta's security automation, some API deployments were disconnected from the WhatsApp server.

If your number was affected, you will get an error such as: code: 1014, title: 'Internal error', details: 'Connection refused. Please check if wacore is running: when trying to perform operations.

Alternatively, the health check will return:

"gateway_status": "unregistered"

If this happens, please create a Support Ticket with us (Category: Messaging Has Completely Stopped Working) and we will re-register the number as per Meta guidance.

We are aware of the issue that is affecting messaging and some other services.

Our engineering team is currently working on a fix for it

We are aware of an issue with the Meta Graph API that is impacting the 360dialog Hub (number onboarding, migrations and status updates). Our engineering team is currently investigating with Meta Support.

We are aware of an issue with the Meta Graph API that is impacting the 360dialog Hub (number onboarding, migrations and status updates). Our engineering team is currently investigating with Meta Support.

We are aware of an issue that is occasionally affecting the Embedded Signup process. If you get stuck on the 'number setting setup' screen for more than 10 mins, it is likely because the User Token required to complete the setup has expired. As a workaround, we recommend the following steps:

1. Logout of Facebook

2. Login to Facebook

3. Redo the Embedded Signup Process

   Our engineering team is currently working on a way to improve this process.

If the workaround fails, create a ticket with our Support Team and we will assist you.

We are aware of an issue that is impacting the Embedded Signup process. If the Embedded Signup flow is aborted before completion, we incorrectly receive a success callback from FB / Meta servers and the user will be logged into the 360dialog Hub. There, they will see a message "we are setting up your number" indefinitely.

If this happens, we suggest:

• Log out of the 360dialog Hub
• Redo the ES flow

Facebook / Meta are currently investigating the issue.

Message from Meta: We are aware that business are unable to send messages to a consumer if the consumer initiated the WA thread between the two parties and the business sends a message after 7 days.

The work-around is to remove the stale check from the send message path

We are aware of an issue that is impacting our Ticketing Service in the 360dialog Hub. Some users cannot view ticket content. Our engineering team is currently investigating it and we'll update again as soon as possible.

We are are receiving reports that the Embedded Signup process is stalling at the "setting up number" screen. We recommend that you PAUSE using Embedded Signup until further notice.