Hello,
I am encountering an issue with the WhatsApp Business API when attempting to send a message template or query the list of templates. The API returns the following error:
{ "error": { "message": "(#135000) Generic user error", "type": "OAuthException", "code": 135000, "error_data": { "messaging_product": "whatsapp", "details": "Generic user error" }, "fbtrace_id": "Acl4jwcxw9wDcwCcNs-_4jW" } }
Relevant Information:
The template used is approved in the Business Manager. The recipient's number has been tested and is in E.164 format (e.g.: +5511999999999). The access token used has the correct permissions (whatsapp_business_messaging and whatsapp_business_management). The phone number is active and linked to the WhatsApp Business account. Sending individual messages continues to work The problem occurred without any changes, sending templates simply stopped working.
Attempts to resolve:
I checked the template parameters and they are correct. I confirmed that the access token is valid. I tested with other templates and other phone numbers, but the error persists.
Has anyone faced this issue or know how to solve it? Is there anything I can check or adjust in the template configuration, or in the WhatsApp Business account to solve this? Is there a support channel by phone or email with Meta?

Tag:-

12 comments.

  1. Mattia

    Also facing this issue. Here is an example of the error: { "error": { "message": "(#135000) Generic user error", "type": "OAuthException", "code": 135000, "error_data": { "messaging_product": "whatsapp", "details": "Generic user error" }, "fbtrace_id": "Ana0BO4kJfSwqKQ2S_26eCS" } }
    The problem occurs with EVERY template, both marketing and utility ones, and they never gave this kind of problem before Friday morning. In the dashboard we don't see any kind of problem and the account's quality is high, all our templates are approved and active. This is causing a serious damage to our activity, as the templates are vital for our customer service.

  2. Waqar

    We are also facing the same issue. It seems like a meta-wide issue. We have yet to see an official response from Meta. We are using two different platforms for the API. On one platform, we were partially able to solve this by adding a fresh copy of the same template, which works fine. On the second platform, this solution didn't work out, and we are yet to see some progress/solution for that.

  3. Arpit

    Had the same issue last week. resolved it by contacting developer support
    https://developers.facebook.com/community/threads/1784341932324611/

    1. Arpit

      Had the same issue last week. resolved it by contacting developer support
      https://developers.facebook.com/community/threads/1784341932324611/

      1. Arpit

        Had the same issue last week. resolved it by contacting developer support
        https://developers.facebook.com/community/threads/1784341932324611/

    2. Arpit

      Had the same issue last week. resolved it by contacting developer support
      https://developers.facebook.com/community/threads/1784341932324611/

  4. Hemant

    Also facing the same issue from yesterday. Everything is setup as it is.

  5. Riekert

    Also facing this issue. Templates that have been sending without any issues are now doing this.

  6. Leonardo

    I am writing to express my concern and disappointment regarding the ongoing issue with our messaging templates, which has persisted since December 28th. Despite submitting two support tickets, the problem remains unresolved, significantly affecting our business operations and customer interactions.
    Each attempt to send a template message results in the following error:
    { "error": { "message": "(#135000) Generic user error", "type": "OAuthException", "code": 135000 } }
    This issue occurs with all templates except for "hello_world," which is the only template successfully delivered.
    In your previous responses, I was advised to check all parameters, which I have thoroughly reviewed and confirmed are correctly configured. Additionally, I was directed to consult the developer section, but no solution to this issue is provided there.
    Given the severity of the impact on our operations, I kindly request that this matter be escalated and resolved as a priority. A generic user error is too ambiguous to address effectively without further clarification or action on your part.
    Please acknowledge this email and provide a detailed resolution plan at the earliest.
    Thank you for your immediate attention to this matter.

  7. Waqar

    Still no support. Meta support where are you?????

  8. Vojta

    Same issue here 29.1.2025, any solutions for you guys?

  9. Krishna

    Same issue Generic user error

Add a new comment.