No posts are being created

Diagnosing an Aimogen Pro rule that produces nothing, in the order that resolves it fastest.

Symptoms#

A rule is configured and enabled, but no posts appear. Either nothing happens at all, or the rule reports running with no output.

First, isolate the layer#

Does a manual run work?

Use Run Now on the rule.

This single test halves the problem, and it is the step people skip.

Generation is failing#

Work through in order.

1. Is the plugin switched on?#

Settings › General Settings › Plugin Main Switch. With it off, nothing generates anywhere.

2. Is the licence activated?#

Settings › Activation. Without it, the feature screens are not offered.

3. Does the API key work?#

Settings › API Keys, then Test API key next to the key the rule uses.

An untested key is the most common cause of a rule that silently produces nothing. If the test fails, see API and provider errors.

4. What does Activity Logs say?#

System & Logs › Activity Logs. This carries the actual error.

If it shows the rule ran with no error, continue. If it shows an error, match it against API and provider errors.

5. Was a request made at all?#

System & Logs › Usage Logs. Look for a row at the time of the run.

6. Is the model still valid?#

Open the rule and check every model selector. A model retired in a plugin update fails with model_not_found.

This is the usual cause when a rule that worked yesterday stops working after an update. See Selecting models.

7. Is content being rejected before publishing?#

Several settings reject generated content rather than publishing it:

Aggressive word filters make a rule appear to do nothing. Remove them temporarily and retest.

8. Is the queue empty?#

Process Each Title/Topic Only Once marks entries as consumed. Once every keyword has been used, the rule has nothing left to do.

Check the keyword list, and the aiomatic_processed_keywords option if you have database access. Add new keywords, or turn the setting off if you want it to cycle.

9. Is duplicate prevention blocking it?#

Overwrite Existing Posts off, combined with titles matching existing posts, means nothing new is created.

10. Is the rule actually enabled?#

Active on the rule. Inactive rules are skipped by the scheduler but still run manually — which is exactly the pattern where manual works and scheduled does not.

Specific creators#

YouTube rules produce empty or generic posts. Captions were not retrieved, so the model only had the title. A TranscriptAPI key is the fix.

Amazon rules find no products. The search term is too narrow, the marketplace is wrong, or scraping is being blocked. Try an ASIN directly to isolate it.

CSV rules process only the first row. Wrong delimiter, or the per-run limit is 1.

OmniBlock workflows produce nothing. Usually a missing output block. See OmniBlocks troubleshooting.

Posts are created but not visible#

Check the post status. A rule set to draft creates drafts. Check Posts › Drafts.

Check the post type. A rule set to a custom post type puts posts there, not in Posts.

Check the publish date. With Set a Custom Post Publish Date Range set in the future and status future, posts are scheduled rather than published.

Check the author. Filtering the post list by your own user hides posts published as another.

Still nothing#

Collect and open a ticket:

1. System & Logs › System Info
2. The Activity Logs entry for the failed run
3. The Usage Logs rows, or confirmation that there are none
4. Which creator, and its model
5. Whether Run Now works

Related#

• API and provider errors
• Scheduled tasks do not run
• Bulk creator: keywords and titles