360Dialog - Hinweisverlauf

We are receiving reports that Users are receiving error responses when trying to create Media Templates.

``` \"message\":\"HSM Template creation failed\", \"type\":\"OAuthException\", \"code\":200002, \"errordata\":\"UserKarmaFilter \", \"errorsubcode\":2388109, \"istransient\":false, \"errorusertitle\":\"Message Cannot Be Submitted\", \"erroruser_msg\":\"This message template cannot be created.\", ```

This error response is coming directly from Meta servers. We have an open case with Meta Direct Support. We are awaiting for their feedback about the issue.

We are aware of an issue that is impacting messaging a small set of numbers.

The team has identified the problem and is working on a fix and we will update again as soon as possible.

We are aware of an issue that is impacting our template management API (4xx errors on template creation). Our engineering team is currently investigating the issue.

We are aware of an issue that may be impacting the loading speeds of the 360dialog Hub and APIs. Clients may be experiencing delays while loading pages, searching and performing other actions in the 360dialog Hub. Our WhatsApp API messaging speeds may also be slightly degraded. Our engineering teams are investigating these issues now. Please wait for new updates, which will be shared here as soon as they are available. We do not have an ETA for resolution at the moment.

We are aware of the logging issue with the 360dialog Hub. Auth0 has an outage, which affects the logging

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.