← All field notes

What should happen when a WordPress automation stops halfway?

An automation backs up a site, updates a plugin, then stops before the last check. Pressing Run again feels harmless. It may also repeat work that already finished.

Before scheduling a workflow across client sites, learn what a retry means. A useful execution record tells you which steps completed and which step was interrupted.

A saved recipe and a queued run are different things

Suppose you queue a recipe, then edit its third step while it is waiting for a worker. The queued run should not silently acquire a new instruction. Otherwise, the reviewer approved one workflow and the site received another.

IrmaWP snapshots recipe steps when a run is dispatched. Its retry path uses the persisted execution log to skip steps already recorded as completed. That keeps an ordinary retry from taking another backup or repeating a completed update solely because a later step failed.

There is still an awkward case: an action might have reached the site just before the worker stopped, without a completion record returning. Treat that step as uncertain. Check the site’s state before retrying work that could produce a duplicate or a destructive change. No generic retry mechanism can make every external operation safe automatically.

Test one deliberate interruption

Use a disposable site and a low-risk workflow. Confirm that its targets are correct and that recovery exists. Interrupt a test run through the supported test setup, then inspect the execution history before resuming it. Avoid manufacturing a failure by killing a production server or disabling a client’s connection.

Your acceptance notes should say which steps ran again and why. Another operator should be able to make the same decision from the recorded evidence, without relying on your memory of the test.

Schedules need a calendar, too

Check the chosen timezone and the next-run preview. A monthly task scheduled for a date that does not exist in every month is a different promise from “once a month.” If a workflow calls an AI operation that requires approval, decide who will handle that approval when the schedule fires.

Custom recipes, schedules and webhooks are available on IrmaWP Pro and Agency. Supported actions keep their permission and safety rules; a webhook is not permission to bypass them. Protect its secret as you would any integration credential.

Start with one recipe that replaces a routine your team already understands. Expand its targets only after you can explain a failed run as clearly as a successful one.


Have a correction or a workflow we should cover? Tell the IrmaWP team.