Troubleshooting

Start with the run: FlowMint Workflows → Run History, the run, then the step’s Output / Error. For the settings a step actually ran with, ask the assistant to fetch the run with flowmint_get_run.

No run appears after a form submission

FlowMint did not start one. Check, in order:

• The workflow is enabled. A workflow created without enabled is saved disabled.
• Its form id matches the form exactly.
• The form stores entries. A submission that is not stored starts no workflow.
• No other enabled workflow is bound to the same form. Only the most recently updated one runs.
• The WordPress admin shows no FlowMint notice about Promptless Forms or Action Scheduler.

The run stays QUEUED

With a Retry count of 0, the background queue has not picked it up: WP-Cron fires only when someone visits the site. Load a page; for good, set up a real cron job as in Installation and setup. Pending jobs appear under Tools → Scheduled Actions with the hook fmw_run_workflow.

With a Retry count of 1 or more, a step failed with a retryable error and the run is waiting for its next automatic retry, after 1, 5 or 15 minutes; its Error code says why. See Retries. Up to version 0.9.0 such a run never restarted; updating marks it Failed (retry_stranded) so you can replay it.

A run or step stays RUNNING

The process was cut off mid-step, for example by a PHP error or a server time limit, often during a long delay or a slow upload.

Since 0.11.0 FlowMint notices this, usually straight away and at the latest within about an hour and a half: the run fails with the error code interrupted and you are notified, or, if the step has "on_error": "retry", it is tried again from that step. Each run also asks the server for up to five minutes, so a large upload is not cut off by a 30-second limit. Check the PHP error log for the cause.

On 0.10.0 and earlier the run stays RUNNING; trigger a fresh one.

A value is blank in the email, file name or request

A path that does not exist becomes an empty string and the step still succeeds. Common causes:

• Form values are under data.*, not entry.* or entry.fields.*.
• Step outputs are read by the step’s name, not its type.
• A misspelt field key. Compare with the context snapshot of a completed run.
• entry_files.<key> is a list when two or more files were uploaded.
• A scheduled run has no form data at all.
• The step that should have produced the value was skipped, or failed with on_error: continue.

A dropdown showing a stored value such as joinery instead of its label means the workflow uses data.* where labels.* belongs.

A condition always goes the same way

Check the condition against the rules in Variables and expressions. Check the value compared first: data.* holds option values, not labels. Up to version 0.9.0, a function call sharing its braces with an operator was never called — {{ !has_file(entry, 'photo') }} was always true; write !{{ has_file(entry, 'photo') }} there. From version 0.10.0 both work, and the Workflows screen lists saved conditions whose result changed.

The email step succeeded but nothing arrived

sent: true means WordPress’s mailer accepted the message. Send a test from another plugin to see whether the site’s mail works at all; many hosts block outgoing mail, and an email-sending service plugin that delivers over HTTPS fixes that. If the output says deduplicated: true, the same run had already sent that subject to that recipient.

Google Drive creates folders but files fail

The service account has no storage of its own. Move the target folder into a shared drive and add the service account to it. See Google Drive credential.

A folder FlowMint created cannot be found in Drive

A folder the service account creates in someone’s My Drive belongs to the service account and does not show in search. Open the parent folder by its address, or use a shared drive.

Every Printavo step fails with config_error

When the message says the credential JSON must include “email” and “token”, the stored credential is the token alone. Store it as JSON with email and token; see Printavo credential. Otherwise the step’s email or contact_id setting came out empty. If Printavo answers “Account not active” while its website works, the account’s API access is off on Printavo’s side.

Steps fail with credential_unreadable

The site’s security keys changed, or the database moved to a site with different keys. Store the credentials again.

A scheduled workflow does not run

• It is enabled and its interval is hourly, twicedaily, daily or weekly.
• Tools → Scheduled Actions has a pending fmw_scheduled_workflow_tick action for it. If not, save the workflow again.
• WP-Cron fires; on a quiet site, add a real cron job.
• The time is in the site’s timezone (Settings → General).

Saving a workflow fails

The answer’s errors list says why. “form_id … does not exist in Promptless Forms” means the form must be created first; “Missing required field: trigger” means the definition has no trigger and no form_id.

Every connector tool answers connector_disabled

Turn on Allow Claude Cowork to call this site under FlowMint Workflows → Connector. More connector problems are in Connector setup.

A replay sent a second email or created a second quote

A replay is a new run and repeats every step’s effect. See Replaying runs.

Related pages

• Error Codes — Every error code a FlowMint step or run can record, what usually causes it, and whether FlowMint treats it as retryable.
• Viewing Runs — Find a run in FlowMint Workflows → Run History, read its status and each step's output or error, and know what the record keeps and for how long.
• Conditions and Errors — Skip steps with skip_if, branch with conditional, recover with try_catch and on_error, and what happens to a run that fails, including automatic retries.
• FAQ — Short answers to common questions about FlowMint Workflows, each with a link to the page that covers it in full.