We believe we have resolved the issue preventing global preferences, cross project IDs, and user devices to be updated, and preventing new devices to be added to WCG.

The BOINC database began rejecting these operations on Friday, September 6th, 2024. The error message given would normally indicate the AUTO_INCREMENT value for the ID column in the affected tables had gone out of range. However, it was not out of range for the defined column type, and each affected table continued to increment the AUTO_INCREMENT counter as desired when a query was rejected. Other tables in the database continued to auto_increment normally, and succeed in CRUD operation execution. The common link with the failing operations was a set of database triggers defined on the tables queried, that call user defined functions to log the changes to user data in another table in the same database, and also to send messages about updated user data to other services internally. Dropping and re-creating these triggers and their associated UDFs has resolved the immediate issue, although we still do not understand the root cause. We will continue to monitor this issue and look to build countermeasures in and refactor the triggers in question to prevent a regression.

We apologize for the inconvenience and long turnaround on this fix.

savas, Thanks for looking into this, seems to be working fine for me too.