Overview
Tasks are the individual units of work created when your flows run. Every sync operation — whether triggered by a schedule, a webhook, or a manual action — creates one or more tasks. The Tasks page lets you monitor these operations and investigate any that did not complete successfully.
You can find the Tasks page in the left sidebar of any integration.
Task list
The task list shows a table with the following columns:
Status — the outcome of the task:
Completed — the task finished successfully
Stopped — the task encountered an error and could not complete
In progress — the task is currently running
Action — the flow that created this task (e.g., an order export or a customer sync).
Origin — how the task was triggered:
Schedule — triggered by a scheduling rule
Webhook — triggered by a webhook event
Admin — triggered manually by a user (via Export One or Export Many on the Flows page)
Created — when the task was started.
Completed — when the task finished (or was stopped).
Filtering tasks
Use the filter options at the top of the task list:
Status filter — show only tasks with a specific status (e.g., only stopped tasks to investigate failures).
Origin filter — show only tasks from a specific trigger type (e.g., only scheduled tasks).
Show only tasks with results — a toggle that hides tasks that ran but had nothing to process (e.g., a scheduled sync that found no new records). This is useful for reducing noise when a flow runs frequently but new data arrives infrequently.
Task detail
Click View task on any row to open the task detail page. This page has two sections:
Task details (left)
ID — the unique identifier for this task (UUID format)
Integration — which integration this task belongs to
Task — the flow action that created it (e.g., "Export one Product to Norce")
Data — the input data that was sent to the task (shown as JSON, e.g.,
{"article_nr":"12345"})Metadata — technical details about the task including entity type, action, and which connectors were used for retrieval and storage
Status — the current status badge (Completed, Error, In progress)
Created from — how the task was triggered (admin, schedule, webhook)
Executed by — which user or system account ran the task
Created at — when the task was created
Run again — a button to re-run the same task. Clicking "Run again" creates a copy of the task with the same input data, which is useful for retrying after fixing a configuration issue
Statistics (right sidebar)
A summary of the task's outcome:
Success — number of records processed successfully
Errors — number of records that failed
Ignored — number of records that were skipped (e.g., no changes detected)
Total entities — total number of records the task attempted to process
Task logs
Below the task details, a Logs section shows all log entries specific to this task. This includes:
An Export to CSV button to download the task's log entries for external analysis
Filters for Status, Message, and Reference Number
A log table with columns: Created, Message, Flags, Reference, Status
The Flags column can contain additional context about the error — for example, specific validation messages or API responses from the target platform. This is the most useful section for diagnosing exactly why a task failed.
Understanding task results
A high number of completed tasks means your integration is working as expected.
Occasional stopped tasks are normal — they can be caused by temporary network issues, rate limiting, or individual records with data problems. Check the related Logs for details.
A sudden increase in stopped tasks usually indicates a systemic issue:
A connector has become disconnected — check Connectors
A required setting is missing or invalid — check Configure > Settings
The target platform is experiencing downtime
Retrying tasks
If a task failed due to a temporary issue (like a network timeout or a missing configuration), you can retry it after fixing the root cause:
Option 1 — Run again from the task detail page
Open the failed task and click the Run again button. This creates a new task with the same input data and configuration. This is the easiest way to retry a specific failed operation.
Option 2 — Re-trigger from the Flows page
Go to Flows and use Export One (for a single record) or Export Many (for a batch) to re-process the affected records. This is useful when you want to re-process with updated settings or a different date range.
Tips
Use the "Show only tasks with results" toggle to focus on tasks that actually processed data.
If you are investigating a specific sync issue, note the task's timestamp and use it to find related entries in Logs.
The Origin column helps you understand whether issues are related to scheduling, webhooks, or manual actions — which can narrow down the cause.
Tasks are retained for a limited period. If you need to preserve task history, export related Logs to CSV.