Yes, it seems like it is functioning normally now. It is common to have 70+ results waiting for validation as each workunit it crunched 2-3 times each to ensure no one is running faulty hardware or trying to cheat for credits. I see you do have one mistakenly marked as invalid. This must have happened in the weird in-between period after I told the server to revalidate those types of workunit. I'll have the server revalidate that one tomorrow.

Our project has been running for upwards of 10 years now and we have been crunching literally billions of workunits over those years. As a result of all of your hard work and dedication, we have actually calculated enough results that we have run out of room to store the IDs of all of these results in a normal unsigned integer value (the default data type used for storing IDs in BOINC databases). As a result, on Tuesday night, I updated our database to be able to store IDs in a much larger data type to prevent this issue from happening again during the remaining life of the project. As a result, I also had to quickly patch the BOINC code we run on the server to allow it to use this newly available data type in the database.