Everyone retries. We repair.
A retry sends the same broken file at the same wall and hopes for a different answer. A repair reads what the platform actually said, changes the thing that caused the rejection, and sends it again.
What a retry does
- Sends the identical file again on a timer
- Shows you an error code, or nothing at all
- Gives up after three attempts and marks it failed
- Leaves the cause exactly where it was
- Tells you days later, if the dashboard is open
What a repair does
- Reads the platform's own words about what was wrong
- Says it back to you in plain English
- Changes the thing that caused it, and only that thing
- Publishes again and records what changed
- Tells you it broke and that it is already fixed, in the same message
What the platform says, and what we do about it.
These are the categories of rejection a scheduler runs into constantly. None of them are your fault, and all of them are fixable without you opening the app.
Caption is 3 characters over the limit for this account.
Trimmed at the last word break so the sentence still finishes, then sent it again.
Media rejected: frame rate 60.0002 fps is outside the accepted range.
Re-encoded the file to a frame rate that platform actually takes, left the picture untouched, and sent it again.
Authorization expired. Token is no longer valid for this account.
Held the rest of the queue instead of burning it, and sent you one link to reconnect.
Post rejected: one or more tags are restricted.
Named the exact tag and pulled it, so the post could go out while you decide what to do about it.
Four steps, and you are only in one of them if you want to be.
The platform sends it back. That moment is the one most tools never surface at all.
We take the raw error string and turn it into a sentence about your post.
The cause gets changed. Nothing else about the post is touched.
It goes out, and you are told what was different about the version that landed.
Pick who gets the last word.
This is a setting per account, not a plan tier. Both are included, and you can run one platform on each.
Fix it and tell me
Repairs run and publish on their own. You find out that a post broke and that it is already fixed, in the same message. For the people who want the tool to handle it and would rather not be consulted about a caption being three characters long.
Fix it and wait
The repair still gets done. It just sits in a queue with the change described in plain English until you approve it. Nothing goes out under your name that you did not agree to. For the people who want to see the diff before it ships.
Every failure, its cause, its fix, and whether it landed.
A row for each post that failed. What the platform actually said, what we read that as, what we changed, how long it took to tell you, and whether the second attempt went out.
It exports. That matters for two reasons. It is the only way to prove to yourself that the thing is worth $49 a month, and it is the record that stops us from making a claim on this website that our own data does not support.
One question rides along with each alert: what would this post have been worth if it had just quietly not gone out. That is the only moment the answer is honest.
What we do not promise
We insure notification, never delivery. Publishing depends on platforms nobody here controls. When one of them is down, it is down, and no tool can post through that.
What we own is telling you, diagnosing it, repairing what is repairable, and never marking a post published when it was not. Some failures are not fixable from our side. Those get named, in plain language, with what you would need to change.
There is no catch rate or repair rate on this page yet, because we have not measured ours. The first hundred accounts are how those numbers get made. When they exist they go here, whatever they say.
Get in before the hundred fills.
Send one line about what you post and where. You will hear back from a person, and the price you get is the price you keep.