Aimogen ProDocumentation
Product page Support

Troubleshooting

Symptom-first troubleshooting for Aimogen Pro, with the diagnostic sequence that resolves most problems.

Start with the symptom.

API and provider errorsError messages from OpenAI, Anthropic, Google and the rest, decoded. No posts are being createdRules that produce nothing. Scheduled tasks do not runCron, run locks and stalled agents. Content quality problemsShort, repetitive, generic or wrong output. Image problemsMissing, broken, irrelevant or oversized images. Licensing and updatesActivation failures and updates not appearing. Plugin and server conflictsFirewalls, caching, security plugins and hosting limits.

Feature-specific troubleshooting lives with each feature: chatbot, OmniBlocks, retrieval.

The diagnostic sequence#

Almost every problem yields to this, in order.

1. Is the plugin switched on? Settings › General Settings › Plugin Main Switch. With it off, no menus appear and nothing generates.

2. Is the licence activated? Settings › Activation. Without it, the feature screens are not offered and updates are disabled.

3. Does the API key work? Settings › API Keys, then Test API key. An untested key is the most common cause of silent failure.

4. What does Activity Logs say? System & Logs › Activity Logs carries the actual provider error. This is the single most useful screen in the plugin.

5. Was a request made at all? System & Logs › Usage Logs. A rule that ran with no corresponding request row failed before reaching the provider — that is a configuration problem, not an API problem.

6. What does System Info say? System & Logs › System Info. Several problems diagnose themselves from it: PHP limits, cron state, connectivity, which providers are configured.

The five most common causes#

In the order support sees them:

1. No real cron trigger. Everything works manually; nothing works on schedule. See Scheduled tasks do not run.

2. An untested or exhausted API key. Silent failure everywhere. Use Test API key and check your provider billing.

3. A retired model. After an update, rules referencing a removed model fail with model_not_found. See Selecting models.

4. A firewall blocking admin-ajax.php or /wp-json/. The chatbot does nothing; REST and webhooks

  1. See Plugin and server conflicts.

5. max_input_vars too low. Settings silently revert on save. See Recommended server configuration.

Isolating a conflict#

If a problem looks like a conflict:

  1. Reproduce it reliably.
  2. Switch to a default theme. Retest.
  3. Deactivate other plugins, then reactivate them one at a time, retesting.
  4. Once you have the culprit, check Activity Logs for what it was doing.

Do this on staging if you can.

Before opening a ticket#

Collect:

  1. The output of System & Logs › System Info
  2. The exact error from Activity Logs
  3. The relevant rows from Usage Logs
  4. What you did, what you expected, what happened
  5. Whether it works with other plugins deactivated

Then open a support ticket. The Knowledge Base also carries single-issue articles, many written under the older Aiomatic name.

Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.