Running and scheduling

How Aimogen Pro OmniBlock workflows are executed, scheduled, cached and invoked from other parts of the plugin.

Running manually#

Run Now on the workflow list executes it immediately, showing each block result as it completes. This is the way to test.

Scheduling#

OmniBlock workflows are rules, and they use the same two-level scheduling as the bulk creators:

The master aiomaticaction cron event fires — every 15 minutes by default.
Each active workflow is checked against its own interval, expressed in hours (or minutes with the minute/hour switcher active).

Workflows are rule type 5 in the plugin internal numbering, which matters when running one through WP-CLI, the REST API or the Abilities API.

Everything on Scheduling and the posting cron applies, including run locking and the Clear Running Rules List recovery tool.

Other ways to run a workflow#

Method	How
Webhook	See Triggers and webhooks
WordPress event	The `wp_event_trigger` block
AI Form submission	The `ai_forms_omniblock` block
Chatbot	The `ai_chatbot_omniblock` block, or the `aimogen_execute_omniblock_rule` extension
AI Agent	The `aimogen_rules_engine` tool with `rule_type` 5
REST API	`POST /wp-json/aiomatic/v1/rules`
WP-CLI	`wp aimogen-run <id> 5`
Abilities API	The `aimogen/run-rule` ability with generator `omniblock`

Caching#

Settings › OmniBlocks › Enable OmniBlocks Result Caching caches block results so a repeated run with identical inputs reuses the previous output instead of calling the AI again.

Turn it on when blocks are deterministic and inputs repeat — scraping the same URL, generating from the same fixed prompt.

Turn it off when you want fresh output every run, or when the workflow is triggered by changing external data.

Cached [aicontent] results are stored in the aiomatict_shortcode_rez table with a hash of the inputs. See The aicontent shortcode.

Execution time#

A workflow runs its blocks sequentially in one execution context. Ten AI blocks at 20 seconds each is 200 seconds, which will exceed a default PHP limit.

Mitigations:

Raise max_execution_time. See Recommended server configuration
Split a long workflow into two, with the first ending in a save_post and the second triggered by that post
Use faster models for the intermediate steps
Remove wait_block delays where they are not needed

Monitoring#

Where	Shows
System & Logs › Activity Logs	One entry per workflow run, with errors
System & Logs › Usage Logs	Every API request the workflow made
System & Logs › Live AI Activity	Requests in real time while the workflow runs
The workflow list	Last run time and status

Bulk actions#

The OmniBlocks list supports bulk enable, disable, duplicate and delete. Duplicating is the quickest way to build a variant of a working workflow.

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