Aimogen ProDocumentation
Product page Support

OmniBlocks troubleshooting

Diagnosing Aimogen Pro OmniBlock workflows that produce nothing, stop part-way, or resolve placeholders incorrectly.

The workflow produces nothing#

Symptoms. Run Now completes but no post appears, or a scheduled workflow shows a last-run time with no output.

Likely causes

  1. No output block. A workflow of AI blocks generates text and discards it. It needs a save_post, save_product, send_email, send_webhook or social block at the end.
  2. The output block is not critical and failed silently. Mark it critical and re-run.
  3. An exit_block fired. A conditional took the exit path.
  4. A required placeholder was empty, so the output block had nothing to save.

How to diagnose. Run manually and read each block result. The first block with empty output is where the problem is.

A placeholder renders as literal text#

Symptoms. The published post contains %%ai_text_2%% instead of the generated text.

Likely causes

  1. Identifier mismatch. The block identifier is 2b, not 2.
  2. Wrong prefix. dalle_ai_image produces %%dalle_image_<id>%%, not %%dalle_ai_image_<id>%%. Check the block reference.
  3. Forward reference. The referenced block runs after this one. Blocks execute top to bottom.
  4. Rendering disabled. Don't Render OmniBlock Shortcodes is on under Settings › OmniBlocks.

The workflow stops part-way#

Symptoms. Some blocks ran, then execution stopped.

Likely causes

  1. A critical block failed. Check Activity Logs for the error.
  2. PHP execution timeout. The whole workflow runs in one request. Count your blocks and their realistic durations.
  3. Memory exhausted. Scraping and image blocks are memory-hungry.
  4. A provider error. Check Usage Logs for the failed request and match it against API and provider errors.

The scheduled workflow never runs#

Not an OmniBlocks problem. See Scheduled tasks do not run. The usual causes are no real cron trigger, the workflow being inactive, or a stale entry in the running list.

The webhook returns an error#

ResponseMeaning
Incorrect OmniBlock ID submitted in requestThe omniblockid parameter is missing or has no underscore
Incorrect format for OmniBlock IDsMore than one underscore in omniblockid
404 on the routeEnable OmniBlocks Webhook Functionality is off
403The API key does not match

Also check that a security plugin or WAF is not blocking /wp-json/omniblock/*. See Plugin and server conflicts.

Scraping blocks return nothing#

  1. The page is JavaScript-rendered. A plain fetch gets an empty shell. Enable a headless browser — see Data and utility providers.
  2. The site blocks the server. Try a proxy.
  3. The URL is wrong, redirecting, or behind a login.

Results are identical every run#

Caching is on. Turn off Enable OmniBlocks Result Caching if you want fresh output.

The workflow runs but costs far more than expected#

Count the AI blocks, multiply by runs per day. A loop built with jump_block that does not terminate is the pathological case — check for one. See Controlling cost.

The AI ran a workflow you did not expect#

The aimogen_execute_omniblock_rule chatbot extension is enabled without a restriction. Set OmniBlock List Allowed For The AI To Execute to an explicit allowlist.

Getting help#

Before opening a ticket, collect:

  1. The workflow configuration — block types, order and identifiers
  2. The error text from System & Logs › Activity Logs
  3. The relevant rows from System & Logs › Usage Logs
  4. The output of System & Logs › System Info

Then open a support ticket.

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