Aaronontheweb on dev
name AzureDevops artifacts per … (compare)
I think we concluded that it was inherently unsafe because if the continuation is "never" resumed, the actor is effectively dead and its mailbox will continue to pile up. Pausing processing is anti-responsive.
he said then
There is a compromise that is possible, though: enqueue incoming messages locally until the continuation has been resumed and completed (so that users are not surprised) until the local queue is full, at which point the actor fails. This places a limit on the non-responsiveness while not breaking semantics.