It's a surprisingly common situation: an existing cruncher decides to add a new project, and adds several new hosts dedicated to this new project. Of course, the CPID will only update for the new project if he attaches a host to one of his original projects.
But if he leaves any of his hosts orphaned, then every time they contact the scheduler, they reset the CPID to the old value. The CPID will cycle endlessly, giving unpredictable results in the exported stats.
I think that once a project has the oldest CPID, it should keep that CPID, ignoring later ones and sending the oldest CPID to those hosts that have a later CPID.
This will require a few changes: a CPID timestamp field in the database, which must be passed in the scheduler request and response, so that the server can compare the age of the provided CPID against the age of the stored CPID.
Components: Scheduler, Database, Daemon.
