The flow in case of a missed/skipped or accidentally cancelled payment is still terrible. can’t stress enough how problematic it is that there is no button to pay for an active but unsubscribed masternode…at the end of the subscription, a button is supposed to show up. But for many, it doesn't. Clearly, the wallet knows when that subscription ends, and also knows it is still active as it is receiving rewards.
If your subscription runs out you get the msg in the attached screenshot. However that's not very helpful; As an unpaid masternode is essentially dead and doesn't come back in my experience after restarting and paying, and after assisting with several support issues...For one, there's no way to really re-subscribe(notice there is no button in that screen), for two, even in the past when people were able to...the masternode never came back, and droplet kept getting shut down again. the only real solution was to totally redeploy, which makes this message null and void and even confusing.
Proposed solution: If a masternode is still active, but not subscribed anymore, add a payment button next to it. We had this button early on and I still don't know why we removed it. Then, when user repays, we need to make sure server will stay active.
If a masternode isn't paid, then no need to tell them it needs to be subscribed. Just tell them subscription expired and masternode has shut down, need to deploy a new one
The flow in case of a missed/skipped or accidentally cancelled payment is still terrible. can’t stress enough how problematic it is that there is no button to pay for an active but unsubscribed masternode…at the end of the subscription, a button is supposed to show up. But for many, it doesn't. Clearly, the wallet knows when that subscription ends, and also knows it is still active as it is receiving rewards. If your subscription runs out you get the msg in the attached screenshot. However that's not very helpful; As an unpaid masternode is essentially dead and doesn't come back in my experience after restarting and paying, and after assisting with several support issues...For one, there's no way to really re-subscribe(notice there is no button in that screen), for two, even in the past when people were able to...the masternode never came back, and droplet kept getting shut down again. the only real solution was to totally redeploy, which makes this message null and void and even confusing.
Proposed solution: If a masternode is still active, but not subscribed anymore, add a payment button next to it. We had this button early on and I still don't know why we removed it. Then, when user repays, we need to make sure server will stay active.
If a masternode isn't paid, then no need to tell them it needs to be subscribed. Just tell them subscription expired and masternode has shut down, need to deploy a new one
┆Attachments: 71500900-0f1a9700-2835-11ea-9cc2-abca0c6fecfc.png