Scheduled posts that go out once, on time
Postozo was built to fix the 2 things people hate most in schedulers: posts that fail without a reason, and posts that go out twice.
What you can do
Never posted twice
Postozo marks each attempt before it calls a network. If the network does not answer, it checks whether the post already went live before it tries again. If it cannot tell, it asks you instead of guessing.
Errors in plain English
When a network says no, you see the reason and how to fix it, like which picture shape is accepted.
Safe retries
Short network problems are retried automatically with growing waits.
Fresh sign-ins
Network sign-ins are renewed before they run out. If a channel loses access, its posts wait and your team gets an email.
Separate lanes
Each network has its own queue, so 1 slow network never holds up the others.
Safety sweep
Every 5 minutes, any due post that lost its place in the queue is put back.
How a scheduled post is published in 4 steps
Checked before saving
The post editor checks each network's rules first, so most problems are fixed before the post is scheduled.
Marked before sending
At publish time, Postozo records the attempt before it calls the network. This is what stops double posts.
Confirmed after a timeout
If a network does not answer, Postozo asks the network whether the post exists. It tries again only when that is safe.
Told in plain words
If a post fails, you get the reason and the fix in the app and by email. Fix it and press Retry.
Example: a network times out
At 09:00 a post goes to LinkedIn, X and Facebook. X answers slowly and the call times out. Postozo does not send it again blindly. It looks for the post on X first. If it finds it, the post is marked as published. If it cannot tell, the post is marked "Could not confirm" and your team is asked to check, so your followers never see the same post twice. LinkedIn and Facebook are not held up, because each network has its own lane.
The no double post rule
Before Postozo calls a network, it records the attempt. If the call fails in a way that leaves the result unknown, such as a timeout, it does not send the post again blindly. It first looks for the post on the network. If it is there, the post is marked published. If Postozo cannot tell, the post is marked "Could not confirm" and you decide: paste the live post's link, or retry. A post is never sent twice.
Errors in plain English
When a network says no, you get the reason in plain words and how to fix it, on the post, in the notification and in an email. For example: "The image ratio is not supported. Instagram accepts ratios between 4:5 and 1.91:1." with the fix "Crop the image to 4:5 or 1:1, then retry." Most failures are a picture shape or size, a missing setting, or a channel that needs to be connected again, and the fix says which.
When publishing is paused
If a workspace has no active plan or a payment failed past its 7 day grace, posts are held, not deleted. When publishing comes back, posts whose time passed more than 15 minutes ago move to drafts, so nothing goes out late by surprise, and you get a notification listing them.
Limits and rules
| Double posts | Never: the attempt is recorded before every network call |
| Unknown results | Checked on the network, or marked Could not confirm |
| Errors | Plain message and a fix, by notification and email |
| Paused publishing | Posts are held; more than 15 minutes late go to drafts |
| Retry | By hand, after you read the fix |
What happens at 09:00, step by step
At the post's time, the post joins a queue for its network. Each network has its own lane, so a slow network does not hold up the others. Before the call, Postozo records the attempt. Then it calls the network. If the network says yes, the post is marked published with its link. If it says no, the reason is turned into plain words with a fix, and you are told. If there is no clear answer, Postozo looks for the post on the network before it does anything else.
Common failures and their fixes
| What you see | What to do |
|---|---|
| The access token expired | Reconnect the channel, then retry |
| The image ratio is not supported | Crop the picture to a shape the network accepts, such as 4:5 or 1:1 for Instagram |
| Needs a video in every post | Add a video; TikTok and YouTube only take videos |
| Needs a Business or Creator account | Switch the Instagram account type in the Instagram app |
| Publishing is paused | Check Billing; posts are held, not lost |
Tips to get more from it
- Connect channels with an account that will stay in the team. If that person leaves, the sign-in can stop working.
- Read the fix in a failure email before you press Retry. Most failures are a picture size or a missing setting.
- Send the post failed webhook to n8n, Make or Zapier if you want failures in Slack or your ticket tool as well as by email.
Words on this page, explained
| Could not confirm | The network did not answer clearly and the post was not found, so you decide. |
| Retry | Send a failed post again, after fixing what the message says. |
| Held post | A post that waits because publishing is paused. |
Mistakes to avoid
- Pressing Retry before reading the fix. Most failures need a change first.
- Connecting channels with an account that may leave the team.
- Ignoring "Could not confirm". Check the network and link the live post, or retry.
Who it is for
- Agencies cannot afford a client post that goes out twice or not at all. See Agencies.
- Marketing teams get a clear reason instead of "Unknown error". See Marketing teams.
- Busy owners get an email only when something needs them. See Small business.
Plans and limits
The same publishing engine runs every plan. There is no premium lane. See Pricing for every limit.
| Limit | Standard | Team | Pro | Ultimate |
|---|---|---|---|---|
| Double post protection | Yes | Yes | Yes | Yes |
| Plain English errors with a fix | Yes | Yes | Yes | Yes |
| Failure emails | Yes | Yes | Yes | Yes |
Works with these channels
Reliability works on every connected channel. These are the ones people use it with most:
See all channels, or compare Postozo with other tools on the compare page.
What if a post fails?
You get a message and an email with the reason and the fix. Fix the post and press Retry.
What does "Could not confirm" mean?
The network did not answer and Postozo could not check if the post went live, so it asks you to check before it tries again.
What if a channel loses access?
Its posts wait instead of failing one by one, your team gets an email, and a webhook can tell your own tools. Reconnect the channel and the posts continue.
Does a slow network delay the others?
No. Each network has its own lane with its own limits.
Why is my scheduled post not posting?
The usual reasons are a channel that lost access, a picture with the wrong shape or size, a missing setting like a YouTube title, or a network that was down. Postozo shows the exact reason and the fix on the post and in an email.
Why is my scheduled Instagram post not posting?
Instagram needs a Business or Creator account, at least 1 photo or video, JPEG photos between 4:5 and 1.91:1, and no more than 30 hashtags. Postozo checks these before you save, so most problems are fixed early.
What does Could not confirm mean?
The network did not answer clearly, and Postozo could not find the post. You decide: link the live post or retry.
Do I get an email when a post fails?
Yes, right away, unless you turned failure emails off in Settings.
Can I get failures in Slack?
Yes. Send the post failed webhook to n8n, Make or Zapier.
Related features
Calendar
See every scheduled, published and draft post in 1 place. Switch between day, week, month and list, and drag a post to move it.
Read moreTeam and roles
Invite your team and clients to 1 workspace. Each role sees and does only what it should.
Read moreAPI and MCP
A public API, an MCP server for AI apps, a command line tool and signed webhooks, all included in every plan.
Read morePost editor
The post editor sends 1 text to all the channels you pick. Change the text, pictures or settings for a single channel without touching the others.
Read moreStart planning your posts today
Create your account and publish your first post in 5 minutes.
7 day free trial. No card needed.