Composed jobs are slow or stay at 0% before printing

If composed jobs in Caldera take much longer than expected to start printing, the problem may be related to how the source files were imported into FileMan.

Summary

If composed jobs in Caldera take a long time to start printing, remain at 0%, or cause high CPU usage from JDFPrintProcessor, the issue may be related to how the source files were imported into FileMan. Reimporting the files with the correct import option can resolve the delay.

Applies to

• Caldera on macOS
• Composed documents created in Caldera Compose
• V18 or newer

Symptoms

• Composed jobs stay at 0% for a long time before printing starts
• Single-file jobs print normally, but composed or nested jobs are much slower
• macOS Activity Monitor shows high CPU usage for JDFPrintProcessor
• The job eventually continues, but only after a long pause
• In some cases, APPE or image storage errors may also appear

Cause

This issue can be caused by the way files were originally imported into Caldera. In the confirmed case, previously imported items continued to cause slow processing until they were removed and reimported correctly.

Resolution

1. Remove the affected files from the Caldera preview pane or image bar.
2. Clear temporary or spool-related files if needed.
3. Open FileMan and reimport the source files.

4. During import, choose Size instead of Resolution.

   

5. Recreate the layout in Caldera Compose.
6. Send the recomposed job to print.
7. Confirm that processing now starts normally.

If the issue continues

• Test with a newly saved version of the original file
• Flatten the PDF or simplify complex artwork if possible
• Reimport the updated file through FileMan and test again
• Make sure older imported problem files are fully removed before retesting