rest_post_invalid_id, which is a hard 404. My first read was a
deletion, and the memory note says a deleted post is the highest-fidelity churn signal. Then I
listed the site's live posts and found the same article, same title, alive at id 75. Same
story at 227 and 226. Not a deletion. A duplicate.automatedSetupService.ts describe.
Our database tracks the orphan draft and does not know the live post exists, so
wp_post_url is null for both rows and our own outcome data cannot see them.Hi,
Six days in, and your trial ends Sunday, so here is a straight read.
ClearPost has produced twelve posts and eleven of them are live: onion tear chemistry, kefir grains, vanilla and hand-pollination, surströmming, brown eggs versus white, 25 food myths, chili heat, MSG, natto, the prebiotic fibre list, and fermented foods for gut health. That is roughly double the normal trial pace, because you kept pulling the next one forward.
Two housekeeping notes, and the second one is our fault.
The twelfth post, "Kefir vs Yogurt: Same Milk, Different Microbes", is sitting in your drafts instead of published. If that is deliberate, no problem. If not, it is one click.
Now ours. Two posts got delivered to you twice, once published and once as a leftover draft. The published copies are the good ones and nothing on your live site is wrong. The stray draft of "Fermented Foods for Gut Health" is ours to clear, and I will clear it.
What I would keep doing: the fermentation and gut thread is the strongest thing on the site. Kefir, natto, surströmming, prebiotics, and fermented foods all reinforce each other, and the queue keeps going there with sauerkraut, why chocolate turns white, and how yeast raises bread.
Anything you would change? Two days is enough time to act on it.
Christian
| Our record | Live on their site | Verdict |
|---|---|---|
| wp=76, pending_review, url null | id 75, published 2026-08-17, identical title | duplicate |
| wp=227, pending_review, url null | id 226, published 2026-08-21, identical title | duplicate |
wp=246, pending_review, url ?p=246 | no public twin | a genuine draft |
75 and 76. 226 and 227. Consecutive ids mean the two copies were created back to back. One came from the plugin's pull and one from our push. Post 76 no longer exists at all, so somebody already tidied that pair. 227 is still sitting there.
The comment at automatedSetupService.ts says the _clearpost_calendar_item_id
dedup key exists to close exactly this race for the first post. These are not first posts, so either
the key is not sent on the daily path or this plugin build predates it. Worth a proper look, and
not something I should guess at in a customer email.
site_seo_settings.review_before_publish is false here, which should mean
publish directly, and three posts still arrived as pending_review.
blog.eniyiteklif.com showed the identical pattern this morning: setting false, 4 of 6 drafted. Two
sites, same contradiction, same day. That is a pattern rather than a coincidence.
| Claim | Source |
|---|---|
| 12 produced, 11 live | 12 calendar rows with a wp_post_id; 9 tracked as published plus ids 75 and 226 confirmed live |
| Every title named | Fetched from their REST API, all publish |
| "double the normal pace" | 12 posts in 6 days against a 1-a-day plan |
| The Kefir vs Yogurt draft | id 246, rest_forbidden (401), so it exists and is not public |
| Coming up | The actual queue: 08-28 chocolate, 08-29 and 08-31 sauerkraut, 08-30 yeast |
lang="en-US" and their wizard answers.