WhatsApp button taps do not update the order
The customer taps confirm, cancel, or edit on the order-confirmation message, but the WhatsApp badge on /dashboard/orders never changes, or a different order changes.
Why this happens
Because NO_MAPPING means no row for that outboundMessageId (manual send without orderId or failed persistence), DUPLICATE means a repeated Meta retry, and TRANSITION_BLOCKED means a disallowed transition or failed stock release on cancel.
What Vareons does about it
Confirm stores confirmed and protects active leases without changing data.status. Edit stores edit_requested with no stock move. Cancel releases stock first, then moves only a non-terminal order to cancelled on success, then sends a deduped acknowledgement keyed by acknowledgementMessageId. The WhatsApp column shows only under useWhatsAppConnected.
- orders.whatsapp.confirmation — WhatsApp order confirmation: Available
Limitations
Cancel never changes a terminal order. Failed stock release stores the reply without changing lifecycle status and sends a distinct ack. Failed delivery states are terminal.
Related problems
Frequently Asked Questions
The customer tapped confirm but the order never changed, why?
Usually a missing link between message and order, a repeated attempt, or a transition blocked by the order state. Check the logged rejections for the exact state, and confirm the chat column is visible, which signals an active connection.
Does the button on an old message work after resending?
Yes, resending creates a fresh row while the old one stays valid, and the button on the old message updates the same order through the old link. No need to ask the customer to tap again on the new message.
Why is a completed order never cancelled from the chat button?
Because cancellation never alters a final order as a protection rule, and failed stock release stores the reply with no lifecycle change. Handle final orders directly from the dashboard instead of chat buttons.
Last verified: 2026-09-19