When a scheduler sends a post, there are three outcomes:
- Accepted: the network confirms, the post exists.
- Rejected: a clear error (expired token, refused content).
- Unknown: timeout or an ambiguous response. The post may or may not exist.
Many tools quietly fold case 3 into case 1 (green tick) or retry it automatically (possible duplicate).
In GPTpost, case 3 is held for a person to check. Published only ever means the network confirmed it, and failures show the network’s reason.
For API users there is also an Idempotency-Key header, so a retried create call returns the same post.
If you want to poke at it on your own accounts, there is a 14-day trial with no card: https://oraglegpt.org/blog/published-means-confirmed/
Which of the three cases has bitten you most?
You must log in or register to comment.
