Skip to content

[BUG] container missing from multi-essence Flows in v8.2 #240

Closed

Description

@samdbmg

Describe the bug
In TAMS v8.2 multi-essence Flows no longer have a container property, however it is possible to add segments to a multi-essence Flow

Thanks to @danjhd for the initial report

Expected behavior
container, codec et al are retained as in v8.1

Suggested fix
Add the missing flow-technical.json schema

Additional context
This was a regression introduced by #130

Activity

  1. self-assigned this
    on Aug 13, 2026
  2. added theissue type on Aug 13, 2026
  3. moved this from Triage to In Progress in TAMS Community Planningon Aug 13, 2026
  4. added a commit that references this issue on Aug 25, 2026
    34fb31b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

tsc-discussDiscuss this issue at the next TSC meeting

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions