Hi Dave...
Thx for the reply.  Here is what was in effect last night before the overnight issue showed up:  I am running wallets, identical, for heat mining.  On the second wallet I already have the utxooverride=-1 as the last line in the bible.conf file.  As far as I can tell the second machine is not sending out PoDC updates, but I'm not completely sure.  Since the wallets are the same, would I be able to actually tell on the second machine if it sent out an update versus an update going out from the primary machine?  When an update goes out from the primary, does that update also show up in the transaction history on the second machine?  I would think it would since they are copies of each other.

But, I will go ahead and turn off the second machine for now and only run the primary.  You seem to be implying that the problem with the auto-staking should correct itself reasonably soon??  I don't HAVE to run the second wallet, however, adding it gives me quite a boost in my hashrate which puts me up almost always in the top 10 on the leaderboard.  Many times I'm number 3 behind the other 2 really big guys.

If you have further thoughts please let me know.  Otherwise, I will come back and update again in the next day or so when the problem resolves.  I just wish there was a way to recover my superblock payment from today!  

>>Edit>>>right after posting this I went back and double-checked the .conf file of the second wallet and discovered the override=-1 line was NOT there!!  I know what happened.  A few nights ago when the multiple updates came out and there were other problems trying to run more than one wallet, I copied the entire appdata folder for bible pay from the primary machine over to the secondary.  I never went back in to add the override line.  Ughh!   Also, right after posting this I also found out that the auto-staking was back to normal and my utxoweight was my full balance once again.  So, other than missing out on today's payments, I should be back receiving them beginning tomorrow.  If something else pops up I will let you know.  I hate it when it's little mistakes like this that are MY fault!  (Not that I was ever blaming Rob for faulty code...lol)