So what happened is that likely one of your autoprices (since it does it in batches, which you can tell from the progress) hit a timeout/504 error, which stopped the entire process because the page you see couldn't interpret that into a number (since there was no number) to know that there were any left. That's what NaN is, it's essentially javascript being like "uhh what is happening here i was expecting a number this 504 error page is not a number???"

But don't worry because you didn't lose any of your autoprice data at all.. prices are updated before deleting the record from the autoprice queue.

it's most likely that somehow your autopricer queue got doubled.

and, yeah, just refresh if you get the nan thing so it will continue!

Have you experienced this since the update?