A connected account that silently stops working — a social platform integration that used to post fine and now doesn’t, with no obvious error surfaced anywhere — is one of the more frustrating troubleshooting scenarios precisely because the failure happens quietly on the receiving end, not visibly on yours.
Why Webhook Failures Tend to Be Silent
A webhook delivering content to a connected social platform depends on that platform’s endpoint accepting the delivery correctly — if the platform’s side has changed (an expired token, a modified API requirement, a permissions change) without your system being explicitly told, the failure can look like nothing happened rather than producing an obvious, loud error.
The First Check: Is the Connection Still Actually Authorized
Social platform integrations commonly rely on tokens or authorizations that can expire or get revoked — sometimes automatically after a period of inactivity, sometimes due to a platform-side policy change. Confirming the connection still shows as actively authorized, not just configured, is the fastest first check.
Using the "Send Now" Test Post to Isolate the Problem
Rather than waiting for the next real scheduled post to reveal whether the connection works, a manual test post sent immediately isolates the problem faster — confirming definitively whether the issue is the connection itself versus something specific to a particular scheduled job or content type.
Checking for Platform-Side API Changes
Social platforms periodically update their APIs, sometimes in ways that break existing integrations without much advance notice. If a connection that worked reliably suddenly stops, checking whether the platform has announced any recent API changes is worth doing before assuming the problem is entirely on your end.
Reconnecting Rather Than Troubleshooting Indefinitely
For an authorization-related failure specifically, simply disconnecting and reconnecting the account often resolves the issue faster than trying to diagnose the exact underlying cause — a fresh authorization frequently just works again, even when the specific reason the old one broke isn’t fully clear.
Why Regular Testing Prevents This From Becoming a Surprise
A connection that silently failed weeks ago and is only discovered now, because content simply stopped appearing on that platform without anyone noticing, is a worse version of this problem than one caught within a day or two. Testing every connected account on a regular cadence, rather than assuming a working connection stays working indefinitely, catches this failure mode much earlier.
Where to Go Next
For the complete publishing and distribution picture, see the complete guide to publishing, distribution, and site health.
