2.0.9: Hybrid execution
A Cloud workflow no longer has to be all cloud. The steps that need your site now run on your site as part of the same Cloud run, and everything else runs in the cloud. Workflows that Cloud refused before run in Cloud now, with nothing for you to change.
Hybrid execution
- Site steps run on your site. Creating a post, saving to a table, writing a file, parsing a document, sending an email and fetching an image with your own key run on your WordPress site inside a Cloud run. A step that runs on your site costs no credits.
- You see where each step runs. The builder shows on every node where that step will run and why, and tells you before the run how many steps go each way and roughly what it will cost. The execution view shows where each step ran and how long a step on your site took.
- Loops in Cloud. The Loop node now repeats a fixed number of times, or while a condition holds, in Cloud as well as locally.
- Email is sent by your site. A Send Email step always goes out through your own site’s mail setup, in Cloud runs as well as Local, so your sending domain, From address and deliverability stay yours. It no longer costs a credit.
- Generate PDF saves to your media library. The rendered PDF is now an attachment on your own site, not only a link.
Fixes
- A fatal error that could take a site down when the plugin’s scheduled licence check went missing (after a restored backup, a clone or a security plugin clearing scheduled tasks). A site missing that entry now repairs itself on the next page load.
- A post created by a Cloud run carries the author, categories, featured image, product images and custom fields set on the node, and the Post node keeps your Content and Excerpt when a featured image is set.
- A Cloud run that pauses for a human task or a site step picks up where it left off. Approving a task on the Tasks page resumes its run, and each task is labelled with the step and workflow that asked for it.
- Signing in no longer stores the user’s password hash in the options table.
- A busy site runs at most four cloud steps at once, and a run that was accepted but never started is retried automatically instead of sitting at pending.
- The plugin no longer logs or suppresses other plugins’ warnings, and usage statistics are recorded correctly.
Changed
- A Cloud loop set to accumulate returns every iteration, not only the last one.
- The API Call and Firecrawl nodes no longer reach private network addresses. A site that needs this can opt back in with the
wp_ai_workflows_allow_private_network_requestsfilter. - Two features that could never be reached from the builder were removed: the MCP stdio transport and the PostgreSQL option for a knowledge base.