An error indicates the user's fault: they need to correct their input before retrying.
An apology indicates the program's fault: either logic for what had been incorrectly thought to be a rare^2 case is missing, or the program has only been configured to deal with N foos, and the user's input requires more. In the former case, the user needs to get a programmer fix before retrying, but in the latter, maybe they can just reconfigure and rebuild (even better, restart with different env vars?) then retry.
The relevant point of this is that when the user is likely to be another programmer, "reconfigure" can be as simple as editing a static allocation.