Yeah, that is an unusual case.
The “MANUAL_BES_CACHING_REQUIRED” doesn’t really mean anything to BigFix though, that’s just for the benefit of us humans to know that caching is required. BigFix checks the sha1 folder before doing every download. Those of use with Airgapped systems have to precache everything by storing the downloads in the sha1 folder.
In fact, BigFix repeatedly checks the sha1 folder. There have been several times where I’ve sent an action before precaching the download, and realized my mistake when the action download status is showing a server unreachable message. When I obtain the download and import it into the sha1 folder, the open action recognizes the newly-cached file and resumes the distribution to clients.
If you can reproduce the behavior, this is probably worth a PMR. Unless it’s possibly a mistake in renaming the file to match its sha1? In my experience, even where a sha256 is available on the download statement, the file should be named to match its sha1 value.