I'm not sure what is going on.
Did you manually print the job from CWS first? or you executed the script and it's printed?
Please clarify what you did.
I don't see any issue on our end. If the call is delivered, then you should see at CWS that the job gets processed and printed.
The job was previously printed via a hotfolder and is now sitting in the held queue. I'm trying to submit it again asa test using the API so I'm expecting it to process it and print again.
I've enclosed the app code minus the api key, logon details etc.
It looks like its running the 3 functions, loginSample, printJobSample and logoutSample from the output.
By the way, printJobSample function only initiate the action (print) for the existing jobs in your Fiery. So you are technically not submitting the job. Submitting job part is postJobContentSample in this sample file.
Ive tried several job ID's all of which are in the held queue and the same result, no message returned in the printJobSample function.
I've rebooted the server just in case but still the same.
Thanks, yes understand the difference between postJobContentSample and printJobSample.
I've tried some of the other functions as well but nothing so perhaps not a code problem but a system problem, is it to do with https as per the attachment or should it still run even if https isnt installed?
Please let me investigate a little bit. Sorry about the hassle. I can see from your initial post that you have been able to successfully login and logout so I'm not sure.
Three things we'd like to ask. We'd like to narrow down the issue.
1. Please enable getSingleJobSample part to see if the job query comes back ok.
2. Please check the res objet and tell us what it returns.
3. If you are not using admin or operator username, make sure the username you are using in the code has print access.