Issue: Getting 'Unsupported post request' error when accessing /accounts with WABA_ID despite having all required permissions:

• whatsapp_business_messaging
• whatsapp_business_management
• Tech Provider verification
• Full business verification

Error: 'Unsupported post request. Object with ID '[WABA_ID]' does not exist, cannot be loaded due to missing permissions.'

Tried:

• New phone numbers
• Fresh access tokens
• Different WABA_IDs
• Permission resets

Note: Can successfully send messages via API, but contacts API access fails. Request format appears correct, but permissions seem blocked despite having all verifications.

Meta support directs all technical issues to their Developer Forum, but the forum throws a ReactComponent error, making it inaccessible. Left without official support channels to resolve this.

"Unexpected null value for wabaID while adding a phone number in WhatsApp API setup."
When attempting to add a phone number in the WhatsApp API setup, an error occurs stating: 'Unexpected null value for wabaID'. This prevents the number from being linked to the WABA.
Expected behavior: The phone number should be added and verified successfully."
Log in to the Meta Developer portal. Navigate to API Setup under WhatsApp. Click on Add Phone Number. Enter a valid phone number. Select a verification method (SMS or call). Click Next. Observe the error.
Thank you, Peter G.

My conversion limit on WhatsApp is not increasing even after I verified my Facebook Business Manager.

i want to initiate a conversation for marketing purposes so i created a template and it has been apporved by meta , now when i try to send it , no errors but the message is not received even thought i added a payment method , does business verification affect the process of sending as my business is not verified yet

I'm bringing attention back to an important issue since older posts are no longer visible after one month.
About five weeks ago, we discussed a problem with the Flows team regarding a bug introduced in Flows version 6.0. The issue concerns components like radio button groups triggering documented but interfering on-select data exchange during back navigation. This behavior is breaking all existing flows that use on-select data exchange for screen navigation, as users can't navigate back without being immediately redirected to the next screen. While the Flows team previously indicated a fix was coming, I wanted to follow up on the status of this critical issue that's affecting our existing implementations.