What does "Content Bot cannot generate articles" mean? Reading the bot's log
In short: This warning tells you on every WordPress dashboard page that Wiozen Content Bot can't produce articles. It appears in two cases: right away when the API key is rejected or the balance runs out, and for any other error once 3 runs in a row have produced nothing. The "Last error" part shows the real cause, and the details are on the plugin's Log tab. The warning goes away on its own with the first run that produces an article.
When does the warning appear, and when does it go away?
The bot records a result at the end of every run. If the run produced at least one article, the failure counter resets. If it produced nothing and an error occurred, the counter goes up by one. Once it reaches 3, users with administrator rights see a red box on every dashboard page: "Wiozen Content Bot cannot generate articles. No article was generated in the last 3 runs. Last error: ..."
Two errors don't wait for 3 runs, because they won't fix themselves. If the API key isn't accepted (HTTP 401) the warning says "API key was not accepted", and if the balance or usage limit is reached (HTTP 429) it says "Balance or usage limit reached", both on the first run. There's one distinction for 429: if the API's response named a short wait (a temporary rush), it isn't treated as an immediate warning and counts like any other error.
Some runs don't count at all. If no category is active, or the bot couldn't find a topic in a category that isn't already on the site, the run ends with no article but also no API error; such runs neither raise nor reset the counter. There's no dismiss button: fix the cause, get one article out with Run now, and the box disappears.
How do I fix "API key was not accepted" and "Balance reached"?
A rejected key usually means it was deleted in the Wiozen API dashboard, or a manually entered key is missing a character. The quickest fix is to reconnect with the Connect account button at the top of the plugin; every connection creates a new key and writes it into the plugin for you. If connecting fails, see the account connection errors guide.
With the balance warning, the box adds an Add funds link that takes you to the wallet on account.wiozen.com. The bot closes the run as soon as it sees this error, and once you've topped up, the next run works normally.
These two errors, and a missing key, also stop the rest of the run. Every following article would hit the same error, so instead of sending pointless requests the bot ends the run and doesn't move on to the remaining categories. With any other error the run carries on: that article or topic is skipped and the bot moves to the next one.
How do I read the Log tab?
The Log tab keeps the last 60 entries, newest first. Each line starts with the date and time, and lines about a category have the category name in square brackets. Each line's type follows the time: "ok" when an article was produced, "note" for information, and errors in red. The All, Errors and Articles buttons at the top filter the list. The Overview tab shows the latest 5 entries too.
A message starting with "Wiozen API:" is an error returned by the API itself and usually carries the HTTP code or the API's explanation. The other lines describe the bot's own decisions. The common ones:
| Log line | What it means | What to do |
|---|---|---|
| Draft saved / Published | An article was produced. If the editor fixed something, the number of fixes is in brackets. | Nothing. |
| Topic skipped, the site already covers it | The suggested topic answered the same question as an existing post. | The bot looks for another topic; if it happens a lot, broaden the content brief. |
| No new topic could be found for this category in this run | Both the suggestions and the sources led to topics already on the site. | Add new subtopics to the brief or new RSS feeds. |
| Could not select a topic | The topic selection request failed. The bot retries up to 2 times, then suggests a topic itself without the sources. | Wait if it's a one-off; if it repeats, read the "Last error" message. |
| Could not write | Producing or saving the article failed. | The bot tries one of its spare topics; the log shows "Writing another topic instead". |
| Research failed | The web search didn't return. | The article is written without research; it's a one-off hiccup. |
| Could not read feed | An RSS address didn't open or isn't valid. | Try the address in a browser, and remove it from the category if it's broken. |
| Image could not be generated | The article was saved but the featured image couldn't be added. | In a live-publishing category the article waits in drafts and the image is retried automatically. |
| Phrase matches the source word for word | A long phrase in the text is identical to the source article. | The article stays in drafts; change that sentence before publishing. |
| The previous run is still in progress; this run was skipped | A scheduled run landed on top of one still going. | Nothing; if it's frequent, lower the frequency. |
"The previous run was cut off at the ... step" is a different matter: the server stopped the run midway. What to do about it is in the guide on runs stopping halfway.
What does the "Get support" link send?
The warning box ends with a Get support link. It opens the support form on account.wiozen.com and adds two things to it: the plugin version and the error code, for example 1.5.11:wcb_api_401, or 1.5.11:wcb_fails for repeated failed runs. Your site address, key and articles aren't added to the link.
When you fill in the form, pasting the latest red line from the log as it is gets the problem found faster. The Support button at the top of the plugin opens the same form, but without an error code.
No warning, but no articles either: what to check
- If the Next run box on Overview says "late", runs aren't starting at all. The cause is usually WP-Cron; see the WP-Cron guide.
- Make sure at least one category is active on the Categories tab. With none active, the log says "No active category" but no warning appears.
- If a category is set to save drafts, its articles won't show on the site; they wait under Posts → Drafts. The "drafts waiting for review" count on Overview shows this.
- If the log has "Topic skipped, the site already covers it" over and over, the bot is working but the topics your brief covers are starting to run out.
Frequently asked questions
After how many failed runs does the warning appear?
After 3 runs in a row with no article and an error. A rejected API key and an empty balance don't wait; the warning appears on the first run.
How do I dismiss the warning?
There's no dismiss button. Fix the cause and run the bot; the warning clears itself with the first run that produces an article.
What if the balance runs out in the middle of a run?
The bot closes the run as soon as it sees the 429 error and doesn't move on to later categories. After you top up, the next run goes in its normal order.
How far back does the log go?
It keeps the last 60 entries. The Overview tab shows the latest 5 of them.
Does the support link send my site details?
No. It only adds the plugin version and the error code. Your site address, key and article content aren't sent.
If the warning looks different on an older version, update to 1.5.11 from the product page. You can also follow your balance and requests in the Wiozen API dashboard.
More guides: How can you use an AI API from Turkey without a credit card? · How do you connect an OpenAI-compatible API to a tool you already use? · How do you calculate the cost of an AI API? · What should I do if my AI API key has leaked? · How do you generate images with an AI API, and what does one image cost? · Why does my AI API return a 429 error, and how do I fix it? · Why do long AI API requests time out: streaming or non-streaming? · Anthropic Messages API or OpenAI Chat Completions: which one should I use? · What is a context window, and what is a 1 million token context good for? · Which AI model should I choose: deciding by price, context and quality · Why does a reasoning model return an empty answer, and why are thinking tokens charged? · Why is my API balance running out faster than expected? Tracking spend request by request · How do you convert a web page to Markdown to feed it to an AI model? · How do you get AI to write and publish articles in WordPress automatically? · How do you find blog topics from RSS feeds and Google Trends? · Does AI-written content show up on Google and in AI answers? · How do you get internal links into AI-written WordPress articles? · How do you get AI to generate a different featured image for every WordPress post? · How do you write a content brief when an AI writes your blog posts? · What should you watch for when an AI writes recipes for your food blog? · How do you fix errors when connecting a WordPress plugin to your AI API account? · Why does my AI article bot stop halfway in WordPress? "Run is stuck" and LiteSpeed · Why are my scheduled WordPress posts late? WP-Cron and a real server cron · How do I get an AI article bot to write blog posts in English or another language?