Repository navigation
Rename DeleteActorRequest.any_state #1161
Description
Activity
- added a parent issue
on Aug 24, 2026 - moved this to Todo in Substrate Milestones (go/substrate-milestones)
on Aug 24, 2026 Should we also rename it to force?
We used the "any_state" boolean to indicate that this will allow users to delete actors from any state, not just suspended or crashed.
We didn't use "force" because this is not a "force deletion", failed deletion still leaves an actor record (to allow retry). I think "force" is separate from "any-state", if customer calls "force delete actor", we should free up the original actor object ref, and allow creating another actor with the same
(atespace, actorname).- removed a parent issue
on Oct 6, 2026 - added a parent issue
on Oct 6, 2026
In #788 a new field
any_statewas added to allow for force deleteActorresources, irrespective of the Actor state. This looks like a "control" field for delete, so I think it should probably be moved underDeleteOptions. Should we also rename it toforce?