IDM - Job Management - Job status still "In progress"

Mourad Ejjadi

Hi Team,
Please we are facing to a blocking issue regarding the IDM Job Management.
All Job status still "In progress" even when it's triggered by "Test Print"

Could you provide any assistance or suggestions for resolving this issue?

Thank you in advance for help

Anand Sartape

Hi @Mourad Ejjadi,
Looks like this is the issue - ExtendedPrinterInfo Exceeding limit 258000 for sqs ... length is 353209

That's the AWS SQS 256 KB message size limit being blown by the GetPrinters response.
With 57 printers on VST_PRD_SRV_ERPPRD_I01 (and Zebra printers with heavy printerProperties payloads), the extended printer info exceeds what SQS can carry, so the status callback from the Print Service back to IDM never completes - jobs stay stuck in InProgress even though the print itself may have succeeded. Restarting spooler / EC won't fix it because the payload size doesn't change.

Things to try, in order:

1. Cancel stuck jobs in IDM Job Management to clear the queue.
2. Delete obsolete printers from the location - start with ZEBRATEST and any decommissioned Zebra entries no longer physically in use.
3. Split the Print Location. With 57 printers on a single location, break them into smaller groups (target 20-25 per location).
4. Reassign printers in the new locations and update any Output Management references pointing to the old location.
5. Trigger a Test Print on a printer in a smaller/new location. Confirm the job status moves to Complete.
6. Verify payload size by re-checking the Print Service log - the ExtendedPrinterInfo length line should now be well under 258,000
7. If still failing, raise an Infor Support ticket referencing the log entry ExtendedPrinterInfo Exceeding limit 258000 for sqs with the MessageId, so they can investigate driver-level printerProperties bloat on the Zebra printers.