Workflow statuses help you understand the current state of workflows, actions and product executions inside AI Workflows.
Statuses provide visibility into:
processing progress
moderation queues
synchronization states
workflow activity
failed executions
Monitoring statuses is important for managing large scale AI automation pipelines.
Why workflow statuses matter
AI Workflows can process:
hundreds of products
multiple actions
moderation stages
synchronization tasks
Statuses help teams quickly identify:
what is currently running
what requires review
what completed successfully
what failed
where bottlenecks exist
Workflow status levels
Statuses may appear on:
workflows
workflow actions
individual product tasks
synchronization states
Different levels may display different statuses depending on the execution stage.
Common workflow statuses
Waiting
The workflow or action is waiting to start processing.
This may happen when:
execution has not started yet
previous actions are still running
products are waiting in queue
moderation must complete first
Waiting does not indicate an error.
Running
The workflow or action is actively processing products.
During this stage:
AI generation is running
products move through the pipeline
tasks are being completed sequentially
Large workflows may remain in Running status for extended periods depending on:
workflow size
AI provider limits
moderation settings
Awaiting moderation
Generated output is waiting for review before synchronization or continuation.
This may happen when:
editor approval is required
moderator approval is required
confidence scores require manual inspection
Products remain paused until moderation is completed.
Synced
The generated output has been successfully synchronized back into the product data.
Examples:
attributes updated
descriptions synchronized
translations published
Synced status usually indicates successful workflow completion for that task.
Completed
The workflow or task finished successfully.
This means:
all actions completed
moderation completed
synchronization completed
No additional processing is required.
Error
An issue occurred during workflow execution.
Possible causes:
invalid prompts
missing source data
synchronization failures
AI provider limitations
unsupported product data
Error statuses should be reviewed manually.
Paused
The workflow has been paused manually.
While paused:
new products stop entering the workflow
automatic execution stops temporarily
continuous monitoring pauses
Paused workflows can later be resumed.
Action level statuses
Each workflow action may display its own execution status.
Example:
Trigger → Completed
Attribute Extraction → Running
Content Enrichment → Waiting
Translation → Waiting
This helps identify exactly where products currently are inside the workflow pipeline.
Product task statuses
Individual products may also display statuses during execution.
Examples:
waiting for processing
awaiting moderation
synchronized successfully
failed generation
translation completed
This provides detailed visibility per product.
Moderation related statuses
Moderation workflows may introduce additional status behavior.
Examples:
waiting for editor review
waiting for moderator approval
declined output
approved for synchronization
These statuses help teams manage AI quality control.
Synchronization statuses
Synchronization statuses help monitor whether generated content was successfully published back into the connected platform.
Examples:
ready to sync
synced successfully
synchronization failed
awaiting approval before sync
This is especially important for marketplace and webshop integrations.
Understanding workflow progress
Statuses work together with workflow progress indicators.
Examples:
20 of 100 products completed
15 awaiting moderation
5 failed
60 running
This gives operational visibility into workflow execution.
Common causes of waiting statuses
Products may remain in Waiting status because:
previous actions are still processing
moderation queues are not completed
workflows are paused
AI provider limits slow execution
Waiting is often temporary during large executions.
Common causes of error statuses
Error statuses may occur because of:
invalid prompt logic
missing required fields
unsupported content structures
synchronization issues
AI provider rate limits
When errors occur:
inspect the failed task
review prompts
validate source data
rerun after corrections
Managing moderation bottlenecks
Large workflows may create many moderation tasks.
If products remain in Awaiting moderation for long periods:
review moderation queues regularly
optimize prompts for higher confidence
reduce unnecessary approval requirements
This improves workflow throughput.
Best practices for monitoring statuses
Monitor workflows regularly
Especially during large executions:
review running tasks
inspect failed products
track moderation queues
This helps maintain workflow quality.
Investigate repeated errors
Recurring errors often indicate:
weak prompts
invalid source data
incorrect workflow logic
Fixing root causes improves long term automation reliability.
Use moderation strategically
Not every workflow requires heavy moderation.
Examples:
High moderation:
SEO content
marketplace descriptions
customer facing copy
Lower moderation:
technical attribute extraction
automated scoring
validation checks
Pause workflows when needed
If unexpected outputs appear:
pause workflow
review results
adjust prompts or rules
retest
resume execution
This prevents large scale issues.
Example workflow status flow
Example:
A workflow processes 500 pet food products.
Status progression:
Trigger → Running
Attribute Extraction → Running
Content Enrichment → Awaiting moderation
Translation → Waiting
Approved products → Synced
Workflow → Completed
The workflow overview allows teams to monitor every stage centrally.