Force a re-authentication when a profile has failed a publish, has stopped syncing analytics for 48 hours, changed owner, changed password, or has a campaign launching within 7 days. Everything else can wait for the automatic refresh.
TLDR: A stale connection is cheap to fix and expensive to discover late. Use the five triggers below, and reconnect any profile that has a launch inside a week before it matters.
Five triggers that justify a forced reconnect
A social connection is a permission token. It expires, gets revoked, or breaks when something changes on the platform side. You don't need to reconnect everything on a schedule. You need to reconnect the profiles that match one of these triggers.
| Trigger | What you see | Action |
|---|---|---|
| Publish failure | A post fails with an authorization or "token" error | Reconnect now, then retry the post |
| Analytics gap | No new data for 48 hours or more | Wait one refresh cycle, then reconnect |
| Password or owner change | Someone changed the login or left the company | Reconnect with the new owner |
| Permission change | A new platform scope or a reduced admin role | Reconnect and re-accept all permissions |
| Launch inside 7 days | A campaign is scheduled on this profile | Reconnect early as insurance |
If a profile matches none of these, leave it alone. Reconnecting for no reason adds clicks and risks granting the wrong account by mistake.
What an expired connection costs, in numbers
In Mydrop's publishing data for September 2026, the most common hard failure was an expired platform connection. Not a bad image, not a caption limit: the connection itself.
That tells you where to spend your attention. A failed post at 9 am on launch day costs far more than ten minutes of preventive reconnecting the week before.
Run a seven-day pre-launch connection check
Do this once for every campaign, on the same weekday each week.
- List the profiles that have posts scheduled in the next 7 days.
- Open each connection and check its status and last sync time.
- Reconnect any profile that shows a warning or has not synced in 24 hours.
- Send one test post or open the preview to confirm the right account is attached.
- Note the date, so you know when each profile was last refreshed.
For a team with 20 profiles, this takes about 15 minutes. In Mydrop's calendar you can see every scheduled post by profile, which makes step 1 a quick scan instead of a hunt.
Reconnect the right account, with the right permissions
Most second failures come from the reconnect itself. Check three things before you click approve:
- The account is the one you meant. Agencies often switch between several logins in one browser.
- Every permission box is ticked. Unticking one to move faster is how a profile ends up half-working.
- The role is still admin or editor. A token cannot publish to a page its user no longer manages.
Our guide to what to check when profiles disconnect unexpectedly covers the diagnosis side, and the post on securing agency OAuth connections covers who should hold the logins.
Give each connection an owner and a refresh date
The reason profiles go stale is that nobody owns them. Fix that with a simple sheet: profile name, platform, owner, last reconnected, next check. One person per profile, not one team.
Agencies running many clients can keep this beside the client list. If you manage client accounts in Mydrop, the connection status sits next to each brand, so the sheet only needs the owner and the date.
Three mistakes that make a stale connection worse
Teams repeat the same errors when a profile breaks.
- Retrying the post ten times. If the token is dead, every retry fails. Reconnect first, then retry once.
- Reconnecting from a shared browser session. The platform quietly attaches whichever account is logged in, which is often the wrong one.
- Ignoring the quiet warning. An analytics gap is the early sign. Publishing fails a few days later, usually at the worst moment.
If you reconnect and the error stays, the cause is usually a lost admin role on the page, not the token. Ask the page owner to restore your role, then reconnect again.
Add the 48-hour rule to your handbook today
Write one line in your team handbook: "Any profile that fails a publish or has no analytics for 48 hours gets reconnected the same day, by its owner." Then run the seven-day check before your next campaign launch. If you want your calendar and connections in one place, start free with Mydrop.
Google review
Trustpilot review
Product Hunt comment
