Note:
This is a Developer level doc. If you are unfamiliar working with code and resolving potential conflicts, we recommend you work with a Woo Agency Partner for larger projects, or find a WooCommerce developer on Codeable for smaller customizations. We are unable to provide support for customizations under our Support Policy.
This reference describes how AutomateWoo processes an event-based workflow. It can help developers and store administrators investigate how a workflow moves from an event to its actions. The exact trigger checks depend on the trigger and its settings.
Life cycle of an event-based workflow
↑ Back to topAn event-based workflow starts with an event, such as an order being paid or a subscription being canceled. AutomateWoo handles some events asynchronously through Action Scheduler before the corresponding trigger evaluates them. This background event is separate from a workflow’s own timing.
- Find workflows: The trigger looks for workflows that use it and passes the event data to each one.
- Check eligibility: Each workflow checks that it is active and has the required data. It checks the trigger’s conditions and the workflow’s rules. If a check fails, the workflow does not proceed.
- Run or queue: A workflow set to run immediately proceeds to its actions. Other timing options create a queued event for the calculated date and time. Find queued items under AutomateWoo > Queue.
- Check a queued workflow: When the queued item runs, AutomateWoo checks that the workflow is active, required data is available, and the trigger’s queued-run checks pass. It also checks the workflow rules again if Revalidate rules before run is enabled. That option is enabled by default but can be disabled for a queued workflow.
- Run actions and record results: When the workflow runs, AutomateWoo runs its actions and records a log, except in test mode. Action errors can appear in the log. Find logs under AutomateWoo > Logs.
- Clean up: AutomateWoo resets temporary workflow context after processing. When tracking is enabled, later email or SMS activity may also be recorded for reports.
A queued workflow can fail before its actions run, for example if its required data is unavailable or its trigger checks no longer pass. For investigation steps, see Troubleshooting a workflow. Processing also depends on the site’s background scheduling and environment settings.
