🐛 Describe the Bug
Whenever a user sends out a message from GHL, we receive a webhook, even if it fails with the status Failed. But when the user clicks on the retry button, I think GHL itself deletes the previous message and sends a new message. But we don't receive any webhook that tells that the previous message was deleted. We just receive a brand new webhook with a new message.
📍 API Endpoint
OutboundMessage
✅ Expected Behavior
The webhook should have another field, maybe named parentMessageId, which tells us that the previous message was deleted and this is the new message that was retried.
💻 Screenshots or Code Samples
{
"type": "OutboundMessage",
"locationId": "ezgb5h8dePEYGiwg0WSu",
"versionId": "698de27f462dc22d054c5cf5",
"appId": "698de27f462dc22d054c5cf5",
"attachments": [],
"body": "Hi there",
"contactId": "M96zrsDWGhHNvlX7XagM",
"contentType": "text/plain",
"conversationId": "h0VYhyhDhebobpHpjP9w",
"dateAdded": "2026-02-26T15:40:14.307Z",
"direction": "outbound",
"messageType": "SMS",
"messageTypeId": 2,
"messageTypeString": "TYPE_SMS",
"userId": "hN1nLpe3EmzSU5ybqosH",
"messageId": "cXcYRmGhooTfw05RZhiK",
"status": "failed",
"source": "app",
"from": "+14633484561",
"to": "+923261332423",
"timestamp": "2026-02-26T15:40:15.982Z",
"webhookId": "81bfc249-e54a-44ba-9195-c8763ad29232"
}
{
"type": "OutboundMessage",
"locationId": "ezgb5h8dePEYGiwg0WSu",
"versionId": "698de27f462dc22d054c5cf5",
"appId": "698de27f462dc22d054c5cf5",
"attachments": [],
"body": "Hi there",
"contactId": "M96zrsDWGhHNvlX7XagM",
"contentType": "text/plain",
"conversationId": "h0VYhyhDhebobpHpjP9w",
"dateAdded": "2026-02-26T15:40:27.527Z",
"direction": "outbound",
"messageType": "SMS",
"messageTypeId": 2,
"messageTypeString": "TYPE_SMS",
"userId": "hN1nLpe3EmzSU5ybqosH",
"messageId": "cRwU12SvFwVu2lbvaWSc",
"status": "failed",
"source": "app",
"from": "+14633484561",
"to": "+923261332423",
"timestamp": "2026-02-26T15:40:28.935Z",
"webhookId": "709fdb9b-3fa6-4a8e-8c61-ed7abcab9b6f"
}Product Area
conversations
📋 Use Case
Right now, when we receive a new webhook, we treat it as a new message. So right now, our database is being bloated with faulty data.
🚨 Why Should This Be Prioritized?
This should be prioritized because we need to sync our conversations with that of GHL.
🧠 Additional Context
No response
🐛 Describe the Bug
Whenever a user sends out a message from GHL, we receive a webhook, even if it fails with the status Failed. But when the user clicks on the retry button, I think GHL itself deletes the previous message and sends a new message. But we don't receive any webhook that tells that the previous message was deleted. We just receive a brand new webhook with a new message.
📍 API Endpoint
OutboundMessage
✅ Expected Behavior
The webhook should have another field, maybe named
parentMessageId, which tells us that the previous message was deleted and this is the new message that was retried.💻 Screenshots or Code Samples
{ "type": "OutboundMessage", "locationId": "ezgb5h8dePEYGiwg0WSu", "versionId": "698de27f462dc22d054c5cf5", "appId": "698de27f462dc22d054c5cf5", "attachments": [], "body": "Hi there", "contactId": "M96zrsDWGhHNvlX7XagM", "contentType": "text/plain", "conversationId": "h0VYhyhDhebobpHpjP9w", "dateAdded": "2026-02-26T15:40:14.307Z", "direction": "outbound", "messageType": "SMS", "messageTypeId": 2, "messageTypeString": "TYPE_SMS", "userId": "hN1nLpe3EmzSU5ybqosH", "messageId": "cXcYRmGhooTfw05RZhiK", "status": "failed", "source": "app", "from": "+14633484561", "to": "+923261332423", "timestamp": "2026-02-26T15:40:15.982Z", "webhookId": "81bfc249-e54a-44ba-9195-c8763ad29232" }{ "type": "OutboundMessage", "locationId": "ezgb5h8dePEYGiwg0WSu", "versionId": "698de27f462dc22d054c5cf5", "appId": "698de27f462dc22d054c5cf5", "attachments": [], "body": "Hi there", "contactId": "M96zrsDWGhHNvlX7XagM", "contentType": "text/plain", "conversationId": "h0VYhyhDhebobpHpjP9w", "dateAdded": "2026-02-26T15:40:27.527Z", "direction": "outbound", "messageType": "SMS", "messageTypeId": 2, "messageTypeString": "TYPE_SMS", "userId": "hN1nLpe3EmzSU5ybqosH", "messageId": "cRwU12SvFwVu2lbvaWSc", "status": "failed", "source": "app", "from": "+14633484561", "to": "+923261332423", "timestamp": "2026-02-26T15:40:28.935Z", "webhookId": "709fdb9b-3fa6-4a8e-8c61-ed7abcab9b6f" }Product Area
conversations
📋 Use Case
Right now, when we receive a new webhook, we treat it as a new message. So right now, our database is being bloated with faulty data.
🚨 Why Should This Be Prioritized?
This should be prioritized because we need to sync our conversations with that of GHL.
🧠 Additional Context
No response