HumanSignal / HumanSignal/label-studio
Change the annotation from one labeling interface to other interface getting error
- Dominant language
- TypeScript
- Stars
- 28.3k
- Forks
- 3.7k
- Avg merge
- 14h
- Merged PRs (30d)
- 15
Description
When switching between different labels in Label Studio, a validation error appears and prevents normal annotation workflow. Existing annotations become incompatible with the updated labeling schema.
when I try to change the annotation from one labeling interface to other interface getting error
Error message:
Validation error f85892f2-9df4-4fbb-a2fa-942243961438
Created annotations are incompatible with provided labeling schema, we found:
4 with from_name=label, to_name=image, type=polygonlabels
This happens after modifying or switching label configurations in a project using polygon annotations.
To Reproduce
Steps to reproduce the behavior:
Create a project in Label Studio using PolygonLabels
Annotate several images/tasks
Modify the labeling config:
change name
change toName
rename labels
or switch annotation schema
Open an existing annotated task
Try switching/selecting different labels
Observe validation error
Expected behavior
Existing annotations should either:
remain compatible after minor label changes,
or Label Studio should provide a clearer migration/recovery mechanism instead of blocking annotation interaction.
Screenshots
Add screenshots of:
the validation error popup/message
the labeling config before/after changes
browser console errors (if any)
Environment (please complete the following information):
OS: / Windows 11
Label Studio Version: latest version
Deployment: Docker
Additional context
The issue appears related to schema validation between existing annotations and updated labeling configuration. Existing annotations reference:
from_name = "label"
to_name = "image"
type = "polygonlabels"
After updating the labeling config, these references no longer match the current schema, causing Label Studio to reject previously created annotations.
Contributor guide
Assessment
This issue has not been assessed yet.