Hello Developers
may it possible to add a "Last_heartbeat" Row in the Active Sessions Table of Buddyauth?
The Reason is:
When HB Crashes or Bugges out and you have to close it hard it often isnt able to release the session.
So when you start up the Bot yuo get the Session limit exceeded Error.
The Normal way you do this on a 1-Session Account is easy: kill t.
But when you run, lets say 3 or more, Sesions on the same key you have no way to find out which is the session that is crashed.
The Normal way you then try to kill it is by killing any of those active sessions, which always results in not finding the right one, at least for me
a Timer "seconds past since last Heartbeat" would be great so i could just kill the session that has had no heartbeat for the longest time.
Or you have a other way around?
may it possible to add a "Last_heartbeat" Row in the Active Sessions Table of Buddyauth?
The Reason is:
When HB Crashes or Bugges out and you have to close it hard it often isnt able to release the session.
So when you start up the Bot yuo get the Session limit exceeded Error.
The Normal way you do this on a 1-Session Account is easy: kill t.
But when you run, lets say 3 or more, Sesions on the same key you have no way to find out which is the session that is crashed.
The Normal way you then try to kill it is by killing any of those active sessions, which always results in not finding the right one, at least for me
a Timer "seconds past since last Heartbeat" would be great so i could just kill the session that has had no heartbeat for the longest time.
Or you have a other way around?
