Pharos has had reports of the following error releasing print jobs in a secure release enviroment where there is no job name assigned to the print jobs.
"Failed to release print job"
Blueprint does have a limitation of not being able to release print jobs with no job name to it, in a secure release enviroment. We acknowledge your concern and queries that you might have with regards to this issue, with the current Blue Print that you have. If you require further assistance please contact support@pharos.com to have a proposed work around to it.