Rename a Workflow

Renaming a workflow in Datature Vi changes the display name only. The workflow ID, all training configurations, and the full run history stay exactly as they were.

Before You Start

A workflow you want to rename inside that project

Open your training project

Go to Training in the sidebar and click the project that contains the workflow you want to rename.

You should see

Workflow canvas header showing the updated workflow name

The updated workflow name appears in the workflows list and in all run entries that reference it.

Naming best practices

A clear naming convention makes it easy to compare runs, trace results back to specific configurations, and onboard new team members who need to understand what each workflow does at a glance.

What to include in a workflow name

Pack the most useful identifiers into the name so you can distinguish workflows without opening each one. A good workflow name answers three questions: what domain, what model, and which iteration.

Recommended name segments

Segment

Purpose

Example

Domain or task

The dataset or problem area this workflow targets

PCB, Aerial, Retail

Model name

The base model or architecture

Qwen2.5-7B, Llama-3

Training method

LoRA, full fine-tune, or other approach

LoRA, FFT

Version tag

Incremental version for tracking iterations

v1, v2, v3

Combine these segments with hyphens for readability. For example: PCB-Qwen2.5-7B-LoRA-v2 tells you the domain (PCB inspection), the base model (Qwen2.5-7B), the method (LoRA), and the iteration (v2).

Patterns that work well

Be specific about the model variant

Include the model size or variant identifier. Qwen2.5-7B is more useful than just Qwen when you run the same architecture at different scales.

Use version numbers, not dates

Version tags like v1, v2, v3 track your iteration count. Dates work for one-off experiments but break down when you run multiple workflows in a single day.

Keep names under 40 characters

Long names get clipped in the workflows list and run history. Drop filler words and abbreviate where the meaning stays obvious.

Match names across your team

Pick one naming pattern and stick with it across all workflows in a project. Inconsistent names force teammates to open each workflow to understand what it does.

Patterns to avoid

Common naming mistakes

Pattern

Problem

Better alternative

test, experiment-1, new-workflow

Gives no information about what the workflow does or which model it uses

PCB-Qwen2.5-7B-LoRA-v1

final, final-v2, final-FINAL

Creates confusion about which version is actually current

Use sequential version numbers: v1, v2, v3

2026-04-12-training

Dates alone do not capture the model, method, or domain

PCB-Qwen2.5-7B-LoRA-v3 (check run history for dates)

PCB-Detection-Qwen2.5-7B-LoRA-FineTune-Version-2-April

Too long, gets truncated in the UI

PCB-Qwen2.5-7B-LoRA-v2

Renaming does not affect run history

When you rename a workflow, all past runs keep their original timestamps and metrics. The new name appears across the interface, but your training history stays intact. Rename freely as your convention evolves.

Next steps

Duplicate A Workflow

Create a copy of this workflow to test variations without changing the original.

Delete A Workflow

Remove workflows you no longer need from the project.

Manage Runs

Monitor and control training sessions that use this workflow.