If an article doesn't generate or publish
Rare, and it fixes itself. We retry automatically; you only hear from us if it truly can't be written, or if your own blog platform is refusing posts.
If an article didn't generate. Writing occasionally hits a snag: the AI answers in a broken format, or the service is briefly overloaded. You don't need to do anything. We retry on our own, first after 15 minutes, then an hour, then four hours. The article shows as Didn't generate in your list while that happens, with a Try again now button if you'd rather not wait.
If it still hasn't worked after four tries, it shows as Couldn't write, the next topic in your plan takes that slot so your schedule stays full, and you get one email about it. That usually means the topic itself is a poor fit, not a technical problem. Try again with a different angle, or delete it.
If you used Write it now and it failed, just click Write it now again. Failed attempts never count toward your daily limit.
If your own blog platform stops accepting articles. This only applies if you publish to WordPress, GoHighLevel, or your own website by webhook. When your platform rejects an article, we retry with the same waits. If it's still refusing after four tries, we email you once with the exact message your platform gave us, and the Publishing section of your Site page turns red with that same message. The usual causes are a changed password or application key, an expired token, or a plugin or firewall blocking outside posts. That part is on your platform's side, so we can't fix it from here.
Your articles are never lost. They are written and waiting, we quietly check your connection once a day, and the moment it works again they publish on their own, one every 15 minutes. Reconnecting from your Site page with fresh details makes that happen right away.