What it does
Execution history records every run of every workflow. When something happened — or did not — you can see exactly what, instead of guessing.
What each run shows
- Which steps ran, and which were skipped because a branch was not taken
- What each step was given and what it returned
- The status of every step
- Where the run stopped, if it stopped, and why
How it works
Every run is rebuilt from the steps recorded for it, which is also how FlowWP resumes a run after a delay — the history and the engine read the same record, so they can never disagree. A run with a failed step is never reported as a success, even when other branches finished, because that is how failures stop being noticed. Secrets such as API keys are redacted from everything that is logged.
In practice
A customer says they never got their welcome email. Open the run for their sign-up and see the trigger fire, the condition pass, and the email step return the mail server’s error — then fix the cause and retry that one step.
Details
Run history is on every plan and kept for 30 days on Free and Personal, 90 days on Business and 180 days on Agency. Old runs are cleaned up automatically. FlowWP also registers with WordPress’ own personal data export and erasure tools, so a privacy request covers its run history too.
