I am experiencing it right now.
The answer above just passes the buck in my view... My capture succeeds (well, the console shows a failure but the profile is put on the share and is manually deployable), the deployment succeeds (again, fails in the Console but deploys just fine after the task shows it fails)
I think it gets this status if it finds more files than it can process immediately and has to stack it up somehow - then when it's finished running through the backlog it returns this status (there are no more zip files) as it moves onto looking for PDFs. This would explain why I captured 9 PST files that totalled 32gb and the task succeeded where as when capturing the best part of 7000 docs, zips, xls, pdf etc (total size 1.3gb) the schedued task fails.
The fact is, the tool doesn't fail - which means I think this is a flaw and that either the UMA tool or Provisioning should be able to cope with this gracefully.
So I am about to log a case with Support - I will update this thread when I get the official answer from LANDesk. Cover me, I'm going in...
My guess is their first response will be the stock answer of "Please apply SP1, see if that fixes it!"