tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Workflow logs in WordPress: Task History, re-execute and debug

FlowMattic Task History: a failed workflow run is opened step by step, fixed and re-executed with its original data.

Workflow logs are how you answer “did it run, and what happened?” In FlowMattic, the automation plugin for WordPress, those logs live in Task History: every run of every workflow, each step with the data it was given and the response it got back, and the tools to run it again once you have fixed the cause.

Task History is where you go when a customer says the email never arrived, and it is the proof when it did. This guide walks through the run list, the run details, the statuses, every way to re-execute, and the settings that control retention and failure alerts, with use cases from stores, agencies, SaaS teams and support desks.

What is Task History?

Each time a workflow runs, FlowMattic records a task: the trigger data plus one entry per step, written as the run goes. Task History is the screen that lists those tasks. You find it in the FlowMattic menu as History, and it is open to administrators and anyone with the Manage Workflows permission.

The logs are stored in your own WordPress database, not on a FlowMattic server, and they stay there until the cleanup setting removes them. There is no per-task fee, so a busy workflow costs you database rows, not money.

How workflow logs work in Task History

Find the run

The list shows Workflow Name, the Applications the run used, its Status and a View Details button. Runs started by a test are marked Test Run, and re-executed runs carry a flag with the time they were re-executed. Running and waiting runs update in the list as they progress.

The search box (“Search by workflow name or data…”) matches workflow names and the data inside runs, so you can search a customer’s email address or an order number. Filters opens a dialog with a Workflow picker that searches as you type, a Date Range (Today, Yesterday, Last 7 days, Last 30 days, This month, Last month or Custom range…) and a Status. Tick Use as my default view and Task History opens on those filters each time, for you only. A saved “Last 7 days” keeps moving with the calendar.

FlowMattic Task History screen listing workflow runs with status chips
The Task History list with workflow names, the apps each run used, run statuses and View Details.

Read the run, step by step

View Details opens the run as a list of step cards, each with its app, its event and a status mark, and Previous Task and Next Task buttons to move through the list. Open a step and two tabs appear. Response Data holds what the step returned, such as an API’s exact error. Request Payload holds the inputs the step ran with, dynamic tags already filled, with passwords, tokens and API keys masked. That lets you compare a live run’s values with a test run of the same step.

A step waiting on a Delay shows when the run will continue and a Cancel Delay button.

FlowMattic Task History run details showing step cards and the Request Payload tab
A run opened in View Details, with each step's status and the Response Data and Request Payload tabs.

Fix it and run it again

FlowMattic does not retry failed steps on its own. Instead, Task History gives you four ways to replay work once the cause is fixed:

  • Re-execute runs the whole workflow again from the trigger. The Re-execute Workflow dialog shows the trigger’s fields so you can reuse them as they are or correct one, such as a mistyped email address, before pressing Re-execute now.
  • Re-run this step only, on any step after the trigger, repeats that single step and shows the new result.
  • Run from this step resumes the workflow from the chosen step and creates a new Task History entry. It is not offered for steps inside an Iterator, because those depend on the loop’s item data.
  • Execute in the bulk bar re-runs several selected tasks at once. The same bar can Delete them.

One more button sits on the trigger step of any run not started by a Schedule: Use this run’s trigger data in the builder. It loads that run’s real trigger data into the workflow as the captured response, so you can map fields against what the live event sent instead of an old sample.

Run statuses

StatusWhat it means
SuccessEvery step after the trigger finished without an error.
FailedA step returned an error and no other step succeeded, or a Stop and Error step ended the run.
Partial FailedSome steps succeeded and at least one failed.
OngoingThe run is executing now.
WaitingThe run is paused on a delay, an approval or a queued batch.
InterruptedThe run stopped part way and never finished.
SkippedSkip Duplicate Events stopped the run as a repeat of an earlier event.

When Skip Duplicate Events stops a repeat event, the run is still recorded, with the status Skipped. Its second step reads “Duplicate event skipped” and names the duplicate key and when the first event arrived, so a deduplicated event is never mistaken for a lost one. Re-execute and test runs are never skipped.

Settings that shape Task History

SettingWhereWhat it does
Task History Cleanup (Days)Settings, AdvancedDeletes runs older than this many days, daily. Default 90, range 1 to 365.
Failed Task NotificationsSettings, NotificationsEnable Notifications and a Notification Email to get an email when a run fails.
Error Webhook URLSettings, NotificationsPosts failures to a URL such as a Slack or Discord webhook.
Add Task History Item InfoFlowMattic Tools actionShows your own text in the run’s title in the list, for example an order number.
Stop and ErrorFlowMattic Tools actionEnds the run as Failed with your own error message, which Task History, the failure email and the Workflow Failed trigger report.

Use cases

Answer “the email never came” in two minutes

A store owner searches Task History for the customer’s email, filtered to Today. The run shows the email step failed because the address had a typo. They correct it in the Re-execute dialog and send the receipt again.

Flow: WooCommerce order → Send Template Email (failed) → Re-execute with the corrected email

Recover from a short API outage

A spreadsheet API was down for ten minutes, so runs show Partial Failed: the CRM step worked, the sheet step did not. Run from this step on the sheet step finishes each run without creating the CRM contact twice.

Flow: Form submission → CRM (success) → Google Sheets (failed) → Slack; Run from this step on Google Sheets

Map fields against what a webhook really sends

A SaaS team’s webhook sample was captured months ago and the sender has since added fields. They open a recent live run, load its trigger data into the builder and map the new fields from real values.

Flow: Webhooks by FlowMattic → Task History run → Use this run’s trigger data in the builder → map and save

Make client runs easy to find

An agency running one intake workflow for many clients adds the client and plan to each run’s title, so a support question about Northwind is one search away.

Flow: Form submission → Add Task History Item Info (“Northwind, Pro plan”) → CRM → Send Email

Alert the team on any failure

Internal ops builds one error-handling workflow on the Workflow Failed trigger. Every failure across the site posts to a team channel with the workflow and the error.

Flow: Workflow Failed → Slack message → WP Tables log row

Stop a follow-up that is no longer needed

A support workflow waits three days before sending a “did this solve it?” email. The customer replied on day one, so the agent opens the waiting run and presses Cancel Delay.

Flow: Ticket closed webhook → Delay (3 days, Waiting) → Send Email; Cancel Delay from Task History

Let an AI client read the logs

With FlowMattic’s MCP Server connected to Claude or another MCP client, the Task History tools let it list runs and read what each step sent and received, so you can ask why last night’s import failed.

Flow: MCP client → FlowMattic MCP Server → Task History tools → answer with the failing step

Tips and gotchas

  • Re-execute is the retry. There are no automatic step retries, so watch failures through the notification email, the error webhook or the Workflow Failed trigger, and replay from Task History.
  • Replays run for real. Re-executing a run that creates an order, a contact or a charge does it again. Prefer Run from this step or Re-run this step only when earlier steps already succeeded.
  • Secrets are masked, other data is not. Names, emails and addresses in your runs are stored as they arrived. Set Task History Cleanup (Days) to match your privacy policy.
  • Name your runs. Add Task History Item Info early in a workflow so the list is readable at a glance.
  • Big histories. Searching and filtering read your database, so a shorter retention keeps the screen quick on busy sites.

See the product overview on the Task History page.

Related features

FAQ

Where are FlowMattic workflow logs stored?

In your own WordPress database. Task History reads them from there, and the Task History Cleanup (Days) setting removes runs older than the number of days you choose, 90 by default.

How do I re-run a failed workflow in WordPress?

Open the run from Task History and press Re-execute to run it from the trigger, editing any trigger field first if the data was wrong. To skip steps that already worked, use Run from this step on the step that failed.

Does FlowMattic retry failed steps automatically?

No. Failed runs are re-executed from Task History when you choose. The only automatic retries are for webhooks delivered through FlowMattic Cloud, which keep trying to reach your site for about five days.

Are passwords and API keys visible in the logs?

No. Request Payload masks fields such as passwords, tokens, secrets and API keys, both on the screen and in the Task History tools over MCP. Other data, such as names and email addresses, is recorded as it arrived.

Why does a run say Waiting?

It is paused on a Delay, an approval or a queued batch and will continue on its own. A run paused on a Delay can be stopped with Cancel Delay.

Every plan keeps a full log of every run on your own server. See FlowMattic plans.

More from the blog