Skip to content

Bug: System ID conflict #5439

@davidkpiano

Description

@davidkpiano

XState version

XState version 5

Description

From Discord: https://discord.com/channels/795785288994652170/1456673826439041275

Is it expected that a child actor can't be stopped and immediately started again, if system ids (in actors invoked by the child actor) are used? I get a "Actor with system ID 'foo' already exists. I need to delay the creation of the actor (and without a started actor I can't render my UI, so I have to render a fallback content and delay the actor creation even further to avoid flickering).

Expected result

System ID reused

Actual result

Error

Reproduction

https://stackblitz.com/~/edit/vitejs-vite-whwbcqra?file=src/main.ts

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions