It’s been over a year since I encountered a bug in Instagram Messaging related to rendering buttons in a carousel. Sometimes, a third button from a different carousel element appears on another element within the same carousel. Strangely, this only affects Android devices.
To help illustrate the issue, I created a Node.js demo that sends a carousel with 10 items. The first nine items each contain three buttons, and the last one contains only one button. However, when the 10th item is rendered, it displays the same second and third buttons as the 4th item in the carousel(could be any other item in carousel). This suggests that the problem affects all of us, not just me.
Below is the Node.js code demo so you can test it You will need to install axios , your page access token and your recipient ID for Instagram
``` // Install axios with: npm install axios const axios = require('axios');
// Replace these with your actual values: const PAGE_ACCESS_TOKEN = ''; // your pageaccesstoken const recipientId = ''; //your psid
// Build the carousel elements with dynamic image URLs const elements = [];
for (let i = 1; i <= 10; i++) { // For the 4th and 10th items, create only 2 buttons; for all others, create 3 buttons. const buttons = i === 10 ? [ { type: 'postback', title: Button ${i}-1, payload: BUTTON_${i}_1 }, ] : [ { type: 'postback', title: Button ${i}-1, payload: BUTTON_${i}_1 }, { type: 'postback', title: Button ${i}-2, payload: BUTTON_${i}_2 }, { type: 'postback', title: Button ${i}-3, payload: BUTTON_${i}_3 } ];
elements.push({ title: Item ${i}, image_url: https://placehold.co/600x400?text=${i}, // Dynamic image URL for each item subtitle: Item ${i}, buttons: buttons }); }
// Create the message payload const messageData = { recipient: { id: recipientId }, message: { attachment: { type: 'template', payload: { template_type: 'generic', elements: elements } } } };
// Function to call the Facebook Send API function callSendAPI(messageData) { axios.post(https://graph.facebook.com/v22.0/me/messages?access_token=${PAGE_ACCESS_TOKEN}, messageData) .then(response => { console.log('Message sent successfully:', response.data); console.log(messageData.message.attachment.payload.elements) }) .catch(error => { console.error('Error sending message:', error.response ? error.response.data : error.message); }); }
// Send the message callSendAPI(messageData);

We have a Plivo account and created a WhatsApp Business Account with an Australian phone number purchased from Plivo.
The corresponding Meta dashboard shows the number and did have the number as active, but as we went through the verification process to add a custom name, it was disconnected, and now shows as Offline at the Meta end (disconnected at the Plivo end).
How do we switch it back to online at the Meta end?

We are using the Instagram Insights API to pull in follower by country. We are noticing the response is returning different percentages than the the App is showing us for accounts?
Has anyone experienced this, Do we know any potential reasons for this?
Your help is appreciated

It is incredible that Meta just want to make things complicated. I want to delete a business profile, but they say that I can't do it, without erasing the system user and ads account.
I cannot erase the system user :B And I don't have any ad account. Just a expire card that also I cannot remove...