First place would be to check the “Summary” page of the action status of the console, to see whether all of the downloads have been cached on the BES Server. If there are download errors where the download source is not available, or the patch has been modified and no longer matches the expected sha1 value, etc. those conditions should be evident there.
If the files have made it to your root server, next thing to check would be the available disk space and cache settings of each Relay between the server and your client, followed by the available space and cache settings on your client.
If that doesn’t correct it, check the client logs and search this forum for how to enable the Relay Diagnostics pages.
I believe I’ve seen a catch-22 condition before with large baselines, where the actions were set to precache downloads before running the baseline and the sum of the baselines downloads exceeded the client cache size. The client would download the first few baseline downloads, then delete them to make room to download later components, then delete the later downloads to make space to redownload the first components, and never get arpund to executing any of them. This was several versions back, I don’t know whether the client has already been fixed for that. Workarounds are larger cache sizes or smaller baselines.