Per window/tab, there can be maximum one active LRC. You can create nested conversations within a root/parent LRC. You can probably leave the conversation (becomes a background LRC and eligible for timeout and eventual destruction) and then create a new LRC (active).
This is why we usually use @Begin(join=true) if that method can be re-executed during the same LRC, otherwise you'll get an exception if an LRC is already running and you exec a @Begin method.
java.lang.IllegalStateException: begin method invoked from a long-running conversation, try using @Begin(join=true) on method: startup
If you get to the end of the use case and no longer need the current long-running
conversation, it’s usually best to end the conversation properly rather than abandon it.
However, if you’re not ready to call it quits, then abandoning the conversation is the
appropriate choice. Before deciding to abandon a conversation to allow the user to go
off on a tangent, consider whether it’s more appropriate to suspend the current longrunning
conversation by nesting a new long-running conversation within it.