Audit your publishing failure rate when it passes about 2% over a week, when one platform fails twice in a row, or after any change to a profile, a connection or a template. Otherwise a weekly glance at the failed list is enough.
TLDR: A rate near 1.5% is normal. Audit when it passes 2%, when one platform fails repeatedly, or after a change. The cause is usually a connection or a platform rule, not the post.
Mydrop data, September 2026: in the 30 days to 16 September 2026, 98.5% of posts published through Mydrop went live at the first attempt. The most common warning was a YouTube custom thumbnail rejected because the channel was not phone-verified; the most common hard failure was an expired platform connection. Method in the Mydrop social media benchmarks.
Failures matter because they are silent. A post that did not go out does not email your audience. Only you notice, if you look.
The four triggers that call for a full audit
| Trigger | What it usually means |
|---|---|
| Failure rate above 2% for a week | A systemic cause, not a one-off |
| Same platform fails twice in a row | A connection, permission or rule change on that platform |
| A new profile, client or template was added | Setup is wrong for that profile |
| Someone retries failed posts by hand every morning | The cause is never fixed |
If none of these apply, review the failed list weekly and move on.
Step 1: count honestly
Take the last 30 days. Count posts planned, posts published at the first attempt, and posts that needed a retry or a manual fix. Divide the last two by the first.
Count retries as failures. A post that works on the second attempt still cost someone time, and it may have gone out late.
Step 2: sort failures by cause, not by date
Group each failure under one label.
- Connection expired or permission removed
- Media rejected (size, ratio, format, thumbnail)
- Caption rejected (length, hashtag count, banned characters)
- Platform outage or API change
- Human change (post edited or deleted after scheduling)
The biggest group tells you where to spend the next hour. Our data shows the most common hard failure is an expired platform connection, and the most common warning is a YouTube custom thumbnail rejected because the channel was not phone-verified.
Step 3: fix the cause once, at the source
A retry fixes one post. A cause fixed once fixes the rest of the month.
- Expired connections: reconnect, then set a monthly reminder to check each profile.
- Thumbnails: verify the channel, keep thumbnails in the allowed size and ratio.
- Captions: shorten the template. A scheduler checks before sending, and TikTok caps captions at 2,200 characters with hashtags counted inside, X at 280 weighted characters.
- Media: export at the platform's recommended ratio before uploading.
This guide on stopping failed posts goes deeper on pre-schedule checks.
Step 4: add a check before scheduling, not after
The cheapest fix is a pre-publish check. Mydrop's pre-publish validation flags caption, media and connection issues while the post is still a draft, so the failure never reaches the schedule.
For bulk work, a failed import is a different problem. See what to check when a bulk import fails.
Step 5: set a threshold and an owner
An audit with no owner is a one-time event. Decide:
- Who looks at the failed list each week.
- What number triggers a full audit (2% is a fair start).
- Where the finding is written down, so the next person starts from it.
On a team, put the weekly failed-list check in the same meeting as the content review. Mydrop's calendar shows planned, published and failed posts in one view, which makes the count in Step 1 much faster.
Do the first audit this week
Run Step 1 and Step 2 on the last 30 days. It takes under an hour. In most accounts, a single cause accounts for most of the failures, and one fix removes it. Start free with Mydrop to see failures and warnings per profile in one calendar.
Google review
Trustpilot review
Product Hunt comment
