Have both bit sizes on my machine in the project folder, because, sometimes a 32 bit repair/rush job is sent to my 64 bit 'reliable' machine, which would at least have the job suffix _2 or higher. I have not specified to only receive 32 bit, because then sciences like MIP1 would never be received by this cruncher. So, first check the project folder which versions you have before breaking sweat.

PS, now have 2 64 bit in queue, device done 350 so far.

The work units themselves have no bit size designation until _0 goes out, if one goes to a 64 bit capable host, the copy will too go to a 64 bit capable host. If the copy goes to a 32 bit host, the wingman is required to also process in 32 bit.

Seem to remember that for reasons of expediency, the distribution system does not wait until a 32 bit only capable machine comes by, i.e. 64 bit machines will act as wingman to 32 bit machines, so what I said before might not be entirely right. That's why that config option exists, to only process 64 bit, which is a few percentage points faster, 4 to 8% it's said. Hunters for the last tasks to process will hardly do that, particularly if work for a science is limited to very limited.

Unfortunately mostly 32 bit and 64 bit do not produce the exact same bit for bit result, both copies that are presented for validation have to be processed with same bit size... weìre stuck with this somewhat slower processing at times.