Skip to main content

Workflow Management

Workflow management combines dataset matching conditions with processing steps into pipelines. A pipeline runs automatically when a dataset is stored or its status changes, and performs operations such as format conversion, project import, quality control, annotation, and export. A pipeline is built from three reusable definition types: matching rules, processing rules, and workflows. A workflow references the first two and forms an executable directed graph.

Workflow overview

Prerequisites​

ItemContent
Menu entryManage → Workflow
Route/workflows (redirects to /workflows/overview by default)
Page permissionsView Workflows; the edit pages require Manage Workflows
API permissionsView Workflows (read), Manage Workflows (create, edit, delete, test)
Writable scopeOnly administrators can write global definitions; project definitions require a Project Manager with write permission on the target project
DependenciesAt least one matching rule and one processing rule; execution requires the background task service and execution nodes to be available

The matching rule and processing rule pages are open to users with View Workflows. Pipeline Map, Project Settings, Run Center, Templates, Workflow Management, Quality Standards, Annotation Config, and Export Config are accessible to administrators and Project Managers only; other roles are redirected to Annotation when they open them.

Pipeline Configuration and Runs​

Tabs and Pipeline Stages​

TabRoutePurpose
Pipeline Map/workflows/overviewEntry points for pipeline stages and blueprint preview
Project Settings/workflows/projectProject-level pipeline switches and parameters
Run Center/workflows/runsPipeline run records, status, duration, and details
Templates/workflows/templatesPreview, trial run, and copy of platform standard templates to a project
Workflow Management/workflows/manageWorkflow list, create, edit, delete
Matching rule/workflows/match-rulesDefinition and testing of dataset matching conditions
Processing rule/workflows/action-rulesArrangement and parameter configuration of processing steps
Quality Standards/workflows/qc-rubricsQC rating standards (strictness and metric thresholds)
Annotation Config/workflows/label-configsModels and review policies for automatic annotation
Export Config/workflows/export-profilesExport format, filter conditions, and directory structure

Workflow configuration page

StageCapability
Collection and storageMatching rules, cloud storage rules
Data normalizationFormat conversion and coordinate system handling
Post-processingRuns of custom algorithm templates
Quality assessmentQC rules and rating standards
Annotation and reviewAutomatic annotation and manual review
Delivery and reportingExport rules and quality assurance reports

Matching Rules​

FieldTypeRequiredDefaultDescription
NameTextYesNoneUp to 200 characters
DescriptionTextNoEmptyUp to 500 characters
ScopeEnumYesGlobalGlobal or project
PriorityIntegerNo100Lower numbers are evaluated first
EnableSwitchNoOnDisabled rules no longer take part in matching
LogicEnumYesAndAnd (all conditions met) or Or (any condition met)
ConditionListYesEmptyEach condition consists of a field, an operator, and a value

Matching conditions support the following fields, operators, and values.

ItemValueDescription
Available fieldsname, extension_name, robot_type, sizemb, source_url, remote_url, local_urlRead from the corresponding dataset attributes
Operatorseq, contains, regex, gt, lt, gte, lte, is_null, is_not_nullNull checks do not need a value
Regex flagsi, m, s, u, y, dg is ignored
Size comparisongt, lt, gte, lteUsed for numeric fields such as sizemb

A matching test runs the same matcher on dataset samples and returns the match count, scanned count, and matched samples.

Processing Rules​

A processing rule consists of ordered steps. The edit page offers two input modes: graphical steps and an advanced JSON mode.

ActionIdentifierDescription
Auto renameautoRenameRewrites the dataset name by a regex pattern and target format, with a test dialog
Auto import projectautoImportProjectImports the dataset into a specified project
HDF5 → MCAPio_hdf5agilex2mcap, io_hdf5realman2mcap, io_hdf5dobot2mcap, io_hdf5limx2mcap, io_hdf5unix2mcapConverts HDF5 data from Agilex, Realman, Dobot, Limx, and Unix by collection source
LeRobot → MCAPio_lerobot2mcapConverts a LeRobot dataset to MCAP
AgiBot → MCAPio_agibot2mcapConverts AgiBot data to MCAP
Meituan → MCAPio_meituan2mcapConverts Meituan data to MCAP
Lumos FastUMI → MCAPio_lumos2mcapConverts Lumos FastUMI data to MCAP
zc0touch → MCAPio_zc0touch2mcapConverts zc0touch data to MCAP
SenseXperience → MCAPio_sensexperience2mcapConverts SenseXperience data to MCAP
BVH → MCAPio_bvh2mcapConverts BVH motion data to MCAP
Generate 3D animationio_generateTransformsGenerates a 3D animation artifact from the data
Galbot Proto data to ROS2io_galbotproto2mcapConverts Galbot Proto data to ROS2 data
Run Custom AlgorithmrunAlgorithmCalls an algorithm template registered in Algorithm Management

Workflows and Configuration Objects​

FieldTypeRequiredDefaultDescription
NameTextYesNoneUp to 200 characters
DescriptionTextNoEmptyUp to 500 characters
ScopeEnumYesGlobalGlobal or project
PriorityIntegerNo100Lower numbers run first
EnableSwitchNoOnDisabled workflows no longer trigger runs
GraphDirected graphYesEmptyComposed of matching rule nodes and processing rule nodes

Quality Standards, Annotation Config, and Export Config hold the rating, annotation, and export parameters used when a pipeline runs.

TabMain fieldsValues
Quality StandardsStrictnessLOW, MEDIUM, HIGH
Quality StandardsMetric rulesMetric, condition, threshold, severity (WARNING, CRITICAL)
Annotation ConfigModelModel identifier, confidence threshold, service endpoint
Annotation ConfigReview policyrandom, all, low_confidence, sampling rate 0–100%, minimum number of reviewers
Export ConfigFormatmcap, hdf5_lerobot, hdf5_robomimic, mp4, rosbag2
Export ConfigFilter and structureQC status, minimum duration; path template and compression method (gzip, none)

Run Center​

The Run Center lists pipeline runs in reverse chronological order.

FieldDescription
IDRun number
DatasetDataset that triggered the run
StageData processing stage
StatusRun status; a running run shows the progress percentage
Start timeRun start time
DurationTime from start to completion
ActionsView run details
StatusMeaning
PendingQueued and waiting to run
RunningExecuting, with a progress percentage
CompletedAll steps finished
FailedA step raised an error; the details include the error message

Constraints and Limits​

ItemValueDescription
Name length≤ 200 charactersSaving is rejected when exceeded
Description length≤ 500 charactersSaving is rejected when exceeded
PriorityInteger, default 100Lower numbers take precedence
Global definitionsOnly administrators can writeProject definitions require a Project Manager with write permission on the project
Matching testNon-administrators must specify a projectScans up to 20000 datasets per run and returns up to 50 samples
DeletionSoft deleteDeleted items no longer trigger runs; historical run records are retained
Tab accessPipeline Map, Project Settings, Run Center, Templates, Workflow Management, Quality Standards, Annotation Config, Export ConfigAccessible to administrators and Project Managers only

Troubleshooting​

SymptomPossible causeActionOwner
The workflow does not runThe workflow is disabled, the matching rule is not satisfied, or the priority is lower than another workflowCheck the enable state, verify matches with Test, and adjust the priorityProject Manager, Administrator
The matching test returns no matchesWrong project scope, overly strict conditions, or a field and operator mismatchLoosen the conditions, or test within the target projectProject Manager
The run stays PendingThe background task queue is congested or execution nodes are unavailableCheck the queue and node status in Operations MonitoringPlatform Operations
A processing step failsThe source format is unsupported, an action parameter is missing, or the algorithm run failedCheck the failed step and logs in the run details, fix the issue, and rerunProject Manager, Administrator
Auto rename does not matchThe regex pattern does not match, or the no-match action is set to skipCheck the result in the rename test dialog and adjust the pattern or actionProject Manager
Access to a tab redirects awayThe current role does not meet the access conditions for that tabAsk an administrator to assign permissions, or use the matching rule and processing rule pagesAdministrator
PagePurpose
Algorithm ManagementRegister algorithm templates that processing rules can call
Data ManagementView datasets processed by pipelines
Annotation TasksView automatically created annotation tasks
Data QCQC rules and result inspection
Dataset ExportExport tasks and target formats
Operations MonitoringTask queues and execution logs