Navigation

Navigation section

Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!

Resolved Wallet shows Prem bot as running but its not

dark sage

dark sage

Misfits
Joined
Nov 21, 2016
Messages
1,445
When running a premium bot, my computer had an unexpected shutdown/power loss. After rebooting and setting up a new instance, I noticed I was being charged for 2 Instances saying both are running when I only have account actively running.
Would prefer not to be charged for 2 instances when I'm only running 1

Thanks for help
 

Attachments

  • abyss sessions.jpg
    abyss sessions.jpg
    22.8 KB · Views: 2
  • wallet2.jpg
    wallet2.jpg
    18.5 KB · Views: 3
  • 05-17 13-15-12 - RegalAbyssPro.txt
    578.3 KB · Views: 0
  • 05-17 9 23 31 - spectre.txt
    306 KB · Views: 0
dark sage

dark sage

Misfits
Joined
Nov 21, 2016
Messages
1,445
douglasyc said:
just go on rws and stop then
Click to expand...

RWS doesn't show it running only the wallet which charged me for it 15min after comp had powerloss


(EDIT)
After 30 min of new session running, the other session is no longer showing as active/running
 
Last edited:
snufalufugus

snufalufugus

Joined
Aug 23, 2015
Messages
1,961
I have already refunded the user, but I suggested he post this thread as well because it's obviously a bug in the RM tracking system.
 
fonrus

fonrus

Joined
Dec 1, 2016
Messages
59
The current tracking system works on a granularity of 15-30 minutes but should always err in the favor of the user. Any insights @Arbiter?
 
arbiter

arbiter

Mod Automation
Joined
Jul 26, 2013
Messages
3,044
Snufalufugus said:
I have already refunded the user, but I suggested he post this thread as well because it's obviously a bug in the RM tracking system.
Click to expand...
This is not a bug. The OP said that the computer crashed, so the sessions kept running because the application wasn't safely closed. It ran until the session expired and the transaction ended. This is all desired behavior.
 
aidden

aidden

Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,774
Arbiter said:
This is not a bug. The OP said that the computer crashed, so the sessions kept running because the application wasn't safely closed. It ran until the session expired and the transaction ended. This is all desired behavior.
Click to expand...
While that might be the case in this instance, i've personally seen sessions continue running in rws despite them being closed by the stop button. However, this was on day 1 so i'm not sure if that has since been fixed or not.
 
derk

derk

12 year old normie
Joined
Jan 8, 2015
Messages
2,769
Aidden said:
While that might be the case in this instance, i've personally seen sessions continue running in rws despite them being closed by the stop button. However, this was on day 1 so i'm not sure if that has since been fixed or not.
Click to expand...
That might just be an RWS issue, not a client issue.
 
Top