360Dialog - Geschichte beachten

We experienced an issue which some nodes could not restart in the usual time. This incident was related to previously unseen behavior in unavailability of nodes within our setup. This resulted in an "internal server error" response when trying to perform basic operations such as message sending. The issue started at ~2am UTC and was corrected ~7am UTC. All affected numbers resumed messaging as normal.

We are receiving reports that some users are unable to launch the Embedded Signup flow. Our engineering teams are investigating this 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 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.