Failed posts
A post that fails four tries moves to Needs attention, grouped by reason, with Retry and Dismiss (or all at once); it clears itself 7 days later.
If an automatic or scheduled post fails, EverySqueeze tries it again — four tries in all, waiting longer each time: 5 minutes, then 30 minutes, then 2 hours, always inside your posting hours. Many failures are passing ones (Facebook or Instagram briefly can't fetch the video from TikTok, a platform times out), and the wait gives them time to clear. While it waits, the post says so: Didn't go through on try 1 of 4 (…the reason…) — trying again at …. Only when the fourth try fails does the post move to your failed list instead of silently disappearing — you can see it, and its error, on the Schedule tab, and the bell and a phone notification tell you.
Some errors are final on the first try instead — for example, a duplicate ("already posted"), or a YouTube post with no title or a Pinterest pin with no board. Those land in the failed list right away, with the reason.
Reaching YouTube's daily upload limit is never a failure: the post waits for the limit to reset and moves to the next open slot (see YouTube daily upload allowance used up).
Skipped pins are not failures
An automatic Pinterest pin goes out only with a confidently matched Amazon product. When there isn't one, the pin is skipped on purpose rather than posted blank. Skipped pins are not counted as failed posts: in Needs attention they are one row of their own, Pins waiting · no confident product to pin, with how many there are. Open it for the list (ten at a time, Show more for the rest) and Fix products in Composer. They are left out of the failed count on the Overview, the Schedule tab and the mobile app. To pin one, set its product and schedule the pin again — see Pin skipped, no product match.
Photo posts are not failures either
A TikTok photo post (slides with music) has no video to send. Where carousel posting is on for your account it posts as a carousel on Facebook, Instagram and Pinterest, and only its YouTube post is skipped, listed with YouTube doesn’t support photo posts. Where carousel posting is off it can't be cross-posted yet: if one reaches your schedule, EverySqueeze takes it out of the queue before it is tried, so it never holds a time slot your videos could use, and lists it in its own row in Needs attention, photo posts skipped · carousel cross-posting coming soon. It has no Retry button, sends no phone notification and is left out of the failed count. Photo posts that showed as failed before this change are listed there too. Nothing is deleted. See Photo posts and carousels.
Needs attention: failures grouped by reason
At the top of Schedule › List (and behind the mobile app's Needs attention bar on its Schedule tab) one Needs attention box sums up everything that needs you, as one row per reason with a count: for example 3 possible re-uploads (new TikToks waiting for your answer, see Possible re-uploads), 18 failed · Facebook · Facebook connection expired., 44 Pins waiting, 4 photo posts skipped, and dismissed or cleared failed posts. Posts that failed for the same reason share one row, so the reason is written once instead of on every post. Tap a row to open it: the full reason (with Learn more), Retry all and Dismiss all, then the posts themselves, ten at a time with Show more. A failed post stays in Needs attention until you retry or dismiss it, or until it clears on its own (below).
The box has two halves. Yours to fix holds what wants something from you: possible re-uploads and failed posts (retry it, reconnect, pick a board, answer in Coverage). Nothing to do holds the record: already posted (the video was already on that platform when it was sent again, so the second copy was not posted; View the post opens it when there is a link), skipped Pins and photo posts, and dismissed or cleared failed posts. When only the record is left, the box is titled For your records and loses its red border.
Retry all and Dismiss all ask first, then do exactly what pressing each post's own button would, one post after another, and say how many went through. A post that still needs a status check (its outcome isn't known yet) or an answer in Coverage is left out of Retry all, and the row says so; it stays listed with its own buttons. If any post in the batch is refused, the message names how many and why, and those posts stay in the list.
Retry and Dismiss
Every failed post has two buttons, on its card on the calendar and on its row in Needs attention (and on the mobile app's failed posts):
- Retry puts the same post back in the queue: the same caption, title and platform, due now (inside your posting hours). It goes through every check a scheduled post does, so it is refused, with the reason, when the video is already on that platform, when the post still looks like a possible duplicate, or when an assistant is out of today's posts. Pressing it twice never queues it twice. If you approve automatic posts by hand, a retried automatic post waits for your approval too. Fix the cause first: if the reason says to reconnect Facebook, Retry only works once Facebook is reconnected. If EverySqueeze isn't sure of the post's Amazon product, Retry asks first in the same box as posting: Confirm & schedule saves the product and puts the post back with your link, Pick a different product searches, and Schedule without link puts it back without one.
- Dismiss takes it off the failed list and out of the failed count. Nothing is deleted: it moves to the dismissed or cleared failed posts row in Needs attention, where Show again brings it back (until 7 days after it failed).
A failed post also clears from the list on its own 7 days after it failed, but never without telling you: one line at the top of Needs attention says so and when the next one clears (the calendar card counts its own days down: Clears from this list automatically in N days), and in its last day the notifications bell reminds you, so you can retry or dismiss it first. Cleared ones stay in the dismissed or cleared failed posts row for your records.
In Needs attention, Show on the calendar opens the day the post failed, with its full card. The card shows the video, the whole reason, what to do about it, and both buttons.
A post that failed as a possible duplicate
If a post fails because it is probably already on that platform, EverySqueeze found a post there with the same length and a matching caption and held the post back rather than risk posting it twice (newer reasons say same length and caption, older ones thumbnail match). A thumbnail-only guess no longer holds a post back. The caption is not the problem here: you don't need to rewrite it, and a new caption doesn't change the check. Open Coverage, find the video and answer the possible match (see Confirm or reject a match). Not a match puts the failed post back in the queue by itself; It's there means it already posted, so it leaves the failed list as already posted. You can also press Retry on the failed post. If you answered Not a match and the failed post is still there (for example you answered before EverySqueeze re-queued these by itself), its card says so: press Retry and it posts. The same goes for a post that failed as already posted because of a match you have since rejected.
Failed in the Composer, but not in the failed list
When you post from the Composer and EverySqueeze stops a platform before sending anything, it says Nothing was posted and why. Nothing was sent, so it is not a failed post and is not in this list. When the reason is that the product isn't confirmed (This product isn’t confirmed, so no Amazon link), it is never marked Failed: a box asks first (Confirm & post, Pick a different product or Post without link), and if you closed it, post again and answer the box, or click ✓ This is right on the video's card. See Confirm a product to get your Amazon link.
When the video made it there anyway
A failed attempt stops counting as a failure once the video is on that platform: a later try posted it, EverySqueeze posted it and marked it, or you marked it posted in Coverage. It then shows as already posted, with a link when there is one, and it's left out of the failed count on the Overview and the Schedule tab. A guess such as a possible thumbnail match doesn't count; only a posted mark does.
For one specific case — a YouTube post that failed because of the daily publish limit — EverySqueeze does show whether a later attempt on that same video succeeded or is already queued again, right on the failed entry, so you don't have to go looking.
The bell shows how many failed
The notifications bell at the top of the dashboard and of the mobile app shows a red number while any scheduled post has failed. Tap it to go straight to the failed posts in Needs attention. The same number also counts posts EverySqueeze moved to a new time and automatic posts waiting because auto-post is off, so nothing about your schedule changes without you hearing about it. With phone notifications on, a post landing in the failed list also sends one. The number counts real failures only (never a skipped pin or photo post, never a post that made it there anyway), and it goes away on its own once they're resolved. It's shown in the app only; failed posts are never emailed. Connection problems count on the same bell; in the mobile app, when one is waiting too, the tap lists both (see Connection problems in the bell). An assistant sees the same count as the Schedule they work in. In VA mode, the "Didn't post" count turns red too.
Failed entries sit on the calendar on the day the attempt actually failed. See Why a post hasn't gone out if a post is still pending rather than failed.
A post failed right after an update
If you keep the dashboard or the mobile app open for hours, EverySqueeze can be updated underneath you, and the open page may not understand the newer answers the server gives it — a post can then show as failed when it did not need to. When a newer version is out, a small bar appears at the bottom of the screen: EverySqueeze was updated with a Reload button. Press Reload, then try the post again. The bar never reloads the page for you while you are typing or while a post, upload or setup is running; if you press Reload then, it asks once more (Reload anyway) because unsaved changes would be lost. A page left in the background and untouched for 30 minutes, with nothing unsaved, reloads itself.