I’m experiencing an issue with my WhatsApp Business connection in Make and would appreciate any guidance.
Until approximately two days ago, all my scenarios were working correctly. However, they can no longer be initialized, and I am receiving the following error:
“Cannot initialize the scenario because of the reason 'Failed to verify connection ‘WABA20260409’. [400]”
Some additional details:
No changes have been made on our side regarding the Make connection, Meta App, or WhatsApp Business Account configuration.
The connection had been working properly for several months.
The issue started suddenly about two days ago.
I received the Make notification regarding “Review your WhatsApp Business Cloud mappings”, but as far as I understand, it only referred to the conversation object and should not affect the connection itself.
Reconnecting the account does not appear to resolve the issue.
Has anyone experienced a similar problem recently? Is there any known change from Meta or Make that could cause connection verification failures for existing WhatsApp Business Cloud API connections?
Any suggestions on where to investigate (permissions, system users, access tokens, WABA settings, Meta Business Manager, etc.) would be greatly appreciated.
Thank you in advance for your help.
Error messages or input/output bundles
Cannot initialize the scenario because of the reason 'Failed to verify connection ‘WABA20260409’. [400]
You can click “Credentials” from the main menu and check your WhatsApp integration. There should be an option to “Verify” it. If the option is available then please use it the integration will come live again.
Should it persist deeper debugging might be needed at the level of your WhatsApp business cloud account.
Do you have one whatsapp module or more than one ? There may be one cached unauthorized (wrong credential / type etc) . You can refresh all modules one by one to force clearing the cahced data
I’ve seen a few people mention similar issues over the last couple of days, so it might not be something on your end. If the connection was working and suddenly every scenario started failing with a 400 verification error, I’d try reconnecting the WhatsApp Business account and checking whether the Meta token or permissions have expired. Hopefully it’s just a temporary API issue.
Thank you very much for the information. Unfortunately, the issue is still ongoing. According to Meta’s recommendations, the next step is to unlink the phone number and set it up again, because in my case it appears that the access token has expired.
The main problem is that Make does not provide a way to update or replace the token within the existing connection. Since there is no option to edit that part of the connection, reconnecting the WhatsApp Business account alone does not seem to resolve the issue.
At this point, it looks like the only available option is to completely remove the connection and recreate it from scratch. Have you seen any alternative solution for this situation?
In my case, I only have a Watch Events module. The issue is that this module cannot be verified or reauthorized because the phone number is already linked.
Since the number is already connected, Make does not provide any option to re-enter a new token or refresh the existing authorization. That is why Meta’s recommendation to reconnect the account is difficult to apply in this scenario.
Have you seen any workaround for a Watch Events module when the token has expired and the number is already linked?
Thank you for your answer. In my case, it does not seem to be a temporary issue, as the problem persists and appears to be related to an expired token.
Yes, I had exactly this issue as well; I couldn’t select my existing WABA in the reauthorize. In the end (after 5 days offline) I made the decision to just make a new WABA: 1. Disable two-step verification on the phone number in WhatsApp Manager 2. Deregister the phone number via Graph API: POST /{phone_number_id}/deregister 3. Delete the phone number from the WABA in WhatsApp Manager 4. Reauthorize your Make.com WhatsApp connection and create a new WABA 5. Add the phone number to the new WABA and verify via OTP 6. Register the phone number: POST /{phone_number_id}/register with your PIN
*7. Update your Make.com scenarios with the correct values from the new WABA: Phone Number ID (especially if you use HTTP requests to send messages), template message names and any other WABA-specific references
Actually, before going through all those steps: try this first (since your screenshot shows an issue with verify, I got stuck on reauthorize because I didn’t do the below before verifying):*
1. Re-register your phone number via Graph API: request_code → verify_code → register with PIN 2. Disable two-step verification in WhatsApp Manager 3. Then click the Verify button on your existing connection
*If Verify succeeds, you don’t need to create a new WABA at all. We had to create a new WABA because Verify kept failing for us, but it’s worth trying this simpler path first.
The root cause is the 4 month certificate expiration on Meta’s side.*
We apologize for the frustration caused by this issue. Could you please reach out to our Customer Care team and open a ticket with them? They are equipped with the proper tools and access to help you dig deeper and investigate this.
Thank you so much for the detailed explanation and for sharing the steps you followed. I’ll try the simpler approach first and see if I can get the existing WABA verified before going through the process of creating a new one.
Unfortunately, I can’t seem to find a way to open a support ticket. When I click the link you provided, it only takes me to my organization dashboard, and from there I don’t see any option to create a ticket. Also, the Help (“?”) button doesn’t appear to be working for me.
Could you please point me to the exact location or provide a direct link to submit a support request?
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles
