Zum Hauptinhalt gehen



Printing via REST API: expecting a bad response if printer is disconnected


1 Kommentar

  • Avatar

    were you interrogating the job with a GET request after the initial POST?  Apparently job activity in the system remain in the system for 60 minutes, so you can to a GET with the generated ID of the original job to determine the status....  

    If for some reason you need to not print it before the printer come back online then, (I assuming) you would need to determine all the jobs that are in the state waiting that you want to cancel and use a PATCH to kill them.



Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.