Should we trigger second "Live processing started" after reconnect?

KurrentDB
1

Let’s assume I have following scenario:

  1. Catchup subscription created

  2. Live processing triggered

  3. Connection lost (ethernet cable unplugged)

  4. New events appeared on the server

  5. Cable plugged in and client reconnected

  6. Subscription read events that where created while no connection and subscribe again

7) Question: should we trigger second “Live processing started” after reconnect?

2

I would say yes as it allows the code in question to know whether its in polling-read mode vs live subscription mode. Some code may care about the difference.

3

On other hand it may be confusing for user to see this more then once per subscription.

4

Is there another for entering polling mode etc?