The workflow overview is the central dashboard for managing all AI Workflows inside Elovate.

From this overview, you can:

The overview gives visibility into your complete AI automation environment.

Each workflow card provides information about:

This allows teams to quickly understand the current state of their automations.

Each workflow appears as a separate card inside the overview.

A workflow card represents:

Selecting a workflow opens the detailed workflow view.

Workflows can contain multiple statuses depending on their execution state.

Common statuses include:

Statuses help identify:

When a workflow is running:

Large workflows may take time depending on:

The workflow overview displays progress indicators showing how many tasks have been processed.

This helps you monitor:

Progress visibility is especially important for large catalog operations.

The workflow detail view displays all connected actions visually.

Example:
Trigger → Attribute Extraction → Content Enrichment → Translation

This makes it easier to understand:

Actions execute from left to right in sequence.

The overview may display task related metrics such as:

These metrics help monitor workflow performance and operational load.

Workflows can be paused temporarily.

When a workflow is paused:

This is useful when:

Paused workflows can later be resumed.

Existing workflows can be modified after creation.

You can update:

This allows workflows to evolve with changing catalog requirements.

Every workflow run creates execution tasks for matching products.

Each task moves through:

Execution visibility helps identify:

From the workflow overview, you can access:

This allows teams to review AI generated content directly from the workflow environment.

The overview also helps track synchronization states.

Examples:

This improves operational control over published product data.

The workflow overview transforms AI processing from isolated jobs into a manageable automation system.

Instead of manually tracking separate enrichment and translation jobs, teams can monitor:

from one centralized location.

Good workflow names improve maintainability.

Good examples:

Avoid generic names such as:

Focused workflows are easier to monitor and troubleshoot.

Examples:

This creates cleaner operational visibility.

Large workflows may create moderation backlogs.

Regular moderation review helps:

Before processing large catalogs:

This reduces large scale workflow errors.

Example:
A webshop has three active workflows:

From the workflow overview, the team can:

All workflow activity is centralized in one dashboard.