If products are skipped during workflow execution, they do not match the workflow conditions or cannot continue through the workflow pipeline.
Skipped products are usually caused by trigger configuration, workflow scope or missing product data.
Common causes
Products do not match the trigger
Only products matching the configured trigger rules enter the workflow.
Examples:
Description is Empty
Category equals Shoes
Status equals Enabled
Products outside these conditions are skipped automatically.
Products already contain data
Some actions only process empty or missing fields.
Example:
Shopping Description is Empty
Products with existing shopping descriptions will be skipped.
Workflow scope limitations
The action scope may only target:
specific categories
selected products
certain store views
limited test items
Products outside the configured scope are skipped.
Products failed in previous actions
Workflows execute sequentially.
If a product fails an earlier action, later actions may skip the product automatically.
Moderation or synchronization blocks
Products awaiting moderation or synchronization approval may temporarily appear skipped until review is completed.
How to troubleshoot
Step 1: Review trigger rules
Check whether the skipped products actually match all configured conditions.
Step 2: Inspect workflow scope
Verify:
selected categories
store scope
action scope
test product selection
Step 3: Review product data
Open skipped products and confirm:
required fields are empty
products are enabled
attributes exist
categories are assigned correctly
Step 4: Check previous workflow actions
Review earlier workflow steps for:
failed tasks
moderation delays
synchronization errors
Best practices
Use focused trigger rules
Test workflows on small product groups first
Monitor failed tasks regularly
Avoid overlapping workflows
Review skipped products during testing