Thank you for your reply. It’s a TSP654II.
I’ve been checking via point 1. and 2., only using manual printing the moment.
I have been adding some Log:debug(); to routes file to capture the request from the printer, check the POST response.
The job is returned in the reponse when the job is at qeued status, the job then goes to notified status and I’ve been reverting this in the database to save manually generating jobs.
Is there a log you know of on the printer side? Also, perhaps multiple failed jobs before the printer was setup correctly is stored in memory and stopping the GET request, is there a clear down method on the printer?
However, I have reset back to factory defaults a number of times so this should have cleared anything of this type. Also, I have logged whether the GET route is hit at all and it is not.