Troubleshooting And FAQ

Most issues fall into a few buckets: scheduled runs on shared hosting, AI model errors, form triggers, and cloud reachability. Work through the section that matches what you are seeing. When you contact support, include the diagnostic log (see the last section).

Scheduled workflows do not run on time

WordPress schedules jobs with wp-cron, which only fires when someone visits your site. On low-traffic sites, scheduled runs can be late or skipped. On shared hosting, long runs can also be cut off by the PHP maximum execution time.

You have two good fixes:

Switch the workflow to Cloud. Cloud runs are scheduled server-side and have no PHP timeouts, so they fire on time regardless of site traffic. This is the simplest fix. See Local vs Cloud execution.
Set up a real system cron that hits wp-cron.php on a fixed interval, and optionally disable the default WP-Cron so it does not double-run.

A run times out or stops partway

Long AI calls, big loops, or large documents can exceed your host’s PHP time or memory limit, which ends the run early. Switching that workflow to Cloud removes the PHP timeout because the run happens on our engine, not in a single web request. See Performance and limits.

AI node errors

Invalid or missing key: re-enter your provider key in Settings, and confirm the provider account has billing or credit available.
Wrong provider used: the specialized AI nodes (sentiment, summary, article writer, SEO) now respect the provider you configured. If an older run forced OpenAI, update to the current version and reselect your provider.
Model rejects temperature or token settings: newer reasoning models (for example gpt-5 and o-series) are handled correctly in current versions. If you see a 400 error mentioning an unsupported parameter, update the plugin, then leave temperature and token limits at their defaults for those models.
Rate limited (429): the provider is throttling you. Wait and retry, or reduce how often the workflow runs.

Form trigger does not fire

The plugin triggers from Gravity Forms, WPForms, Contact Form 7, Ninja Forms, and Elementor Forms. If a submission does not start your workflow:

Confirm the form plugin is installed and active.
Open the trigger node and make sure the correct form is selected, and that fields are mapped.
Confirm the workflow itself is active, not just saved.
Submit a real test entry. Some form plugins only fire once the entry is fully saved.

See Trigger Nodes for the full setup for each form plugin.

Cloud cannot reach your site

Cloud runs sometimes need to call back to your WordPress site. If you see a clear “site could not be reached from the cloud” message, your site is not reachable from the public internet. Common causes:

The site is on localhost, a staging URL, or behind HTTP authentication or a firewall that blocks outside requests.
A security plugin or host firewall is blocking the incoming callback.
The site URL in WordPress settings is wrong or points somewhere unreachable.

For sites that cannot be exposed publicly, run those workflows in Local mode instead.

If the chat widget does not appear, confirm the shortcode is placed on a published page. The widget is style-isolated from your theme by design, so theme CSS should not affect it. If replies never arrive, check that the Chatbot node’s provider or credits are configured.

Diagnostic log and getting help

Open Settings and use the diagnostic-log download to save a log file. It captures recent errors without exposing your secrets.

For help, visit wpaiworkflowautomation.com and the rest of these docs. When you write in, attach the diagnostic log and describe which node failed and whether the workflow was running Local or Cloud.