- Community
- Question
We use Instagram Messaging with Facebook Login and a Page access token, subscribed to messages v25.0. Revalidating the existing callback completed successfully, and the corresponding Meta GET challenge reached our endpoint and returned HTTP 200.
Messages visible in the Instagram inbox have not produced corresponding POST requests in our endpoint access log. The official dashboard sample test also reports success without a corresponding observed POST. An unsigned request from our own external machine reaches the same endpoint and is logged, but this does not establish reachability from Meta or exclude failures before HTTP logging.
What official diagnostic is available to confirm whether a messages delivery was attempted, its effective destination, and its HTTP/TLS outcome? Does the dashboard test success message confirm completed HTTP delivery, or only acceptance of the test action?
We are seeking delivery-trace guidance rather than assuming a permissions or networking root cause.
We have a new reproducible delivery observation after restoring the Page–App subscription on September 9. At approximately 07:45 UTC on September 10, 2026, the Instagram professional account's native inbox received a real incoming “Hello”. The receiving account is tingting___xu (IG ID 17841461870729987), associated with Page 1087471007781770 and App 2268597573675118, using API v25.0. The sender shown in the inbox is ataurrahman52.
Our expected callback is https://reception.equiinet.cn/webhook. From 07:40:00 to 07:49:19 UTC, the formal HTTPS access logs, including rotated logs, recorded no POST or webhook-path request. There is no matching application inbound event or signature/binding/parsing rejection evidence. This does not establish whether Meta attempted delivery or whether an attempt failed before HTTP logging.
The September 9 Page subscription restore completed successfully and the readable App subscriptions/callback remained unchanged. Please trace the September 10 message: was an instagram/messages event generated; which App/account mapping and destination URL were used; what were the delivery attempt times, HTTP response or DNS/TCP/TLS failure stage, retry outcome, and correlation IDs? If event generation was suppressed by permissions or sender eligibility, please identify the exact permission/access-level decision for this message. We can provide the native inbox screenshot through an appropriate support channel. We are seeking delivery diagnostics before making further subscription changes or sending duplicate test messages.