Original design of the unlurk process was that when the broadcaster stopped the bot, it would clear any outstanding lurking records.
This process no longer occurs since the bot can run indefinitely. Now the bot needs to detect when the broadcaster has ended a stream, and then update the records at that time instead.
There should be a built in process that identifies if the broadcaster 'disconnected' for some reason. so the Unlurk cleanup should not be automatic to the end of a broadcast. but should record the end of the broadcast datetime as the unlurk event time.
Original design of the unlurk process was that when the broadcaster stopped the bot, it would clear any outstanding lurking records.
This process no longer occurs since the bot can run indefinitely. Now the bot needs to detect when the broadcaster has ended a stream, and then update the records at that time instead.
There should be a built in process that identifies if the broadcaster 'disconnected' for some reason. so the Unlurk cleanup should not be automatic to the end of a broadcast. but should record the end of the broadcast
datetimeas the unlurk event time.