Following length OOB discussion with Robert, following the talk about this in the DM room, this was the course of action decided upon.

Once Gen3 Butler comes along, and supertask, there might be enough context about the ongoing processing to deal with this better, but for now, this reduces chatter and cleans things up.

The problem is that we don't have enough information here to either

1. Log a fatal warning and abort; or
2. Silently proceed

Both are legitimate, depending on the dataset, but the butler doesn't provide enough context (yet).  Logging at WARN level is inappropriate when the data is fine.

Looks good

Merged.