So Im double checking our code, and it appears a person could get out and in like this (for future reference) - say we joined with nickname 'cap' - if you did : exec cpk cap, then exec join pog, then we have "cap" being used.  If you did a new force on the cpk without unjoining pog: exec cpk cap2 email user true, then exec unjoin pog, then exec join pog, you would be fine (as far as I can see).  But just ignore this part for now lets move on to your two accounts.

As far as 'capulinko2' I dont see a config issue:  I see BHKIV* being used for the CPK - and it looks fine, it has your sig, then we have the exec join pog being successful also for the BHIV* (capulinko2).  (On a side note I also see a successful BLUL capulo and BLUL pog capulo).  But moving back to capulinko2, I dont see anything stopping your pog.

Could you please do this - try erasing debug.log, and after a restart, unlock the wallet and try the 'sendgscc pog 2000' again and look in the log and see if there is a specific error message?  It could just be at the time you had < 5 in depth.  And maybe that error was only in the log.

If that does not work, tonight while we are sleeping you can try:  exec unjoin pog, wait 5 blocks, then exec join pog and re-report.  (But I dont see that helping the situation).