@Mike_Wagner and @ning…
(all times in Central Time Zone).
Just a little clarification… I did the vNode withdraw this morning around 9:30am, it had completed earning at 6am this morning. My pNode probably went into earning around the same time, but had not earned any PRV at that time. It is possible that I did the withdrawal of vNode rewards while my pNode was in Earning mode, so maybe that “Withdraw All Rewards” was applied to my pNode, even though it had a 0 PRV balance… So now that we are later in the day and the pNode has returned to “Waiting”, it is possible the “withdraw” command is still pending for the pNode…
So my guess, is that the app is functioning as expected, but because there is no indication that the pNode is pending a withdrawal on the App, and I had initiated a “Withdraw All Rewards” prior to having any PRV in the pNode… So from my user point of view, when I enter the app to withdraw the rewards, I am initiating a new request, while the old request is still pending… I completely understand the process for pNodes is manual, and can take days… been doing this for quite a while… I think the issue is that with the “Withdraw All Rewards” function, it makes the request for pNode, even if no PRV are present (maybe its just because dust is still present)… and me as a user did not realize that request is pending, so upon my return, i am looking to initiate the withdraw request, and app seems “broken” even though the request is already pending from an earlier vNode withdraw request.
I think this is an unintended side effect of the Withdraw All functionality, where user may not realize a pNode withdraw request is made/pending… hence makes the app appear unresponsive, even though the request is actually already pending.