I was bit confused in my description here, sorry. /usr/bin/env existed but when it was run under the cron user's environment it could not locate the interpreter

I was bit confused in my description here, sorry. /usr/bin/env existed but when it was run under the cron user's environment it could not locate the interpreter we required and failed silently. The shebang line worked fine under all other users' accounts. Very frustrating. I assume this problem was due to the cron account's $PATH being set up differently somehow. In any case we just went back to explicitly choosing our site-specific interpreter path. Related pet peeve: people using #!/bin/sh when they really want #!/bin/bash. They are not interchangeable!