Deleting a model alias that a saved workflow names is allowed #2097

Open
opened 2026-11-21 15:04:47 +00:00 by sam · 0 comments
Owner

Why: #2090 added delete for models and aliases on /settings/models. The API refuses only a missing alias, so deleting the default model or an alias a saved workflow still names succeeds, and those workflows fail at run time. The confirmation dialog only warns about it.

Plan: the delete is refused while any saved workflow names the alias, with the error naming those workflows. The governance module asks the runs module through its API package; no cross-module table access. Deleting the default model is refused while any workflow relies on it.

Done when: deleting an alias in use returns a conflict naming the workflows, the dashboard shows that error inline, and deleting an unused alias still succeeds.

**Why**: #2090 added delete for models and aliases on /settings/models. The API refuses only a missing alias, so deleting the default model or an alias a saved workflow still names succeeds, and those workflows fail at run time. The confirmation dialog only warns about it. **Plan**: the delete is refused while any saved workflow names the alias, with the error naming those workflows. The governance module asks the runs module through its API package; no cross-module table access. Deleting the default model is refused while any workflow relies on it. **Done when**: deleting an alias in use returns a conflict naming the workflows, the dashboard shows that error inline, and deleting an unused alias still succeeds.
sam added the lowbug labels 2026-11-21 15:04:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#2097